.NET Framework - "activex control" in VB.net

I have an application containing WMP and I'd like to create an "online"
version of it.  I believe that this used to be accomplished with activex in
VB 6.  How would I go about recreating it for use in websites like youtube,
or other flash players?  Do I have to go back to VB 6?

  dnorri replied...

Can someone tell me if I'm not posting as a "MSDN Subscriber"?  I'm not
getting any response from anyone for my posts...  I thought someone was
supposed to respond in 2 days.

Thanks

  rowe_newsgroups replied...

AFAIK ActiveX is alive and well with on the .Net framework. Since
ActiveX is not my area of expertise, I did a quick search in the
Asp.Net group and found the following thread that may be of use to
you:

http://groups.google.com/group/microsoft.public.dotnet.framework.aspnet/browse_thread/thread/776a0ee59c5ca0e4/12c13dde12ecf77a?lnk=gst&q=windows+media+player&rnum=2&hl=en#12c13dde12ecf77a

Thanks,

Seth Rowe

  dnorri replied...

thanks for the response.

I think I'm just not making myself very clear.  I don't want to embed the
Windows Media Player activeX control into a webpage.  I've created my own
player in VB2005 as  a windows forms project.  Now I'd like to make it into
something like an Activex Control and drop IT into a webpage.
Any ideas?

ContentAlignment (1) GraphicsUnit (1) EventHandler (1) FontStyle (1) CheckBox (1) TextBox (1) Is this a Windows Forms application? If so, there ishould be a region titled is not totally packed with InitializeComponent() { System.ComponentModel.ComponentResourceManager resources = new System.ComponentModel.ComponentResourceManager(typeof(InvoiceForm)); this.textBox17 = new System.Windows.Forms.TextBox(); this.textBox15 = new System.Windows.Forms.TextBox(); this.textBox7 = new System.Windows.Forms.TextBox(); this.textBox6 = new System.Windows.Forms.TextBox(); this.textBox5 = new System.Windows.Forms.TextBox(); this.textBox4 = new System Windows.Forms.TextBox(); this.textBox3 = new System.Windows.Forms.TextBox(); this.textBox2 = new System.Windows.Forms.TextBox(); this.textBox1 = new System.Windows.Forms

windows.forms usercontrol, event and delegate .NET Framework Hi I want to prepare a customcontrol consist of a label, one property LabelText- a text for label control and a window Form. When click on the label the window form should appear and is what you are looking for, besides that I enjoyed writing it :) Jeroen The System.Windows.Forms.Label class already has a Text property. Why do you need another one? It is simple enough to handle the Label control's Click event if you want to do something when the user clicks the mouse button while over the Label control. The Label class already has a TextChanged event, and this event will in fact be not you have an actual object instance? Also, are you trying to create a custom Control sub-class, or a UserControl? There is a difference between the two, and your post Form, but which you can place within an actual Form). Pete actually, a custom Label control is only an example. I work on custom control which is more complicate and the custom Label control is the way to see the

code to throw the exception. using System; using System.Drawing; using System.Threading; using System.Windows.Forms; namespace MyNamespace { public class MyForm : Form { private Label label1; private Button button1; public MyForm the other). Note that you can change the behavior if desired by setting the static Control.CheckForIllegalCrossThreadCalls property to "true". Then the exception will occur with or without the debugger attached but comes down to the issue that the Win32 API itself creates thread affinity for windows and their message queues, and for whatever reason the .NET designers decided to make that safe, because interaction with the controls relies on window messages, which are always marshaled by Windows to the correct thread (the one that owns the control). But a) this implicit marshaling can cause hard-to-debug deadlock problems, and b) makes of the time (i.e. that 100% of the behavior is delegated to the Win32 control via window messages). Even for Forms controls that are in fact based on Win32 controls enhanced behaviors. And for Forms controls that are written mostly from scratch (they all inherit Control, and so all wind up having a window handle at some point???.NET Forms does Note that one major issue is that there are a number of members of the Control class that when accessed will implicitly cause the window handle for that Control instance to

top-most or so. . . Any suggestions are really grateful. Thanks!!!! C# Discussions Visual Studio (1) Windows 7 (1) EventHandler (1) Exception (1) EventArgs (1) Class (1) VB (1) XP (1) try { Enabled = false; } finally { Enabled = true; } Thanks a lot Jeff!!!!!!!! it works scenario, but definitely the same root cause): https: / / connect.microsoft.com / VisualStudio / feedback / details / 581382 / windows-taskbar-can-activate-a-non-modal-window-when-a-modal-window-is-active-wpf-winforms determine the form's behavior WRT the taskbar. The documentation for the ShowInTaskbar property contains VB, C# and C++ examples of "how to use the ShowInTaskbar property to make a dialog box that is not displayed in the Windows taskbar." Each sample has an explicit comment about setting the form's ShowInTaskbar property to form2 to receive focus. . ." If you attempt to reproduce the same behavior with just two windows, one modal and one not, it works differently: selecting the non-modal window from the a window's presence in the taskbar, and with the "live" thumbnail views available in Windows 7, there is every reason to want to keep the window there, even when the not be? The OP offered no reason why it is necessary to show the modal windows in the taskbar. Making the window accessible is the source of the unexpected behavior. The

fillcontrols() bei ReferenzDB.frm_datainput. . ctor() bei ReferenzDB.frm_anmelden.button1_Click(Object sender, EventArgs e) bei System.Windows.Forms.Control.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ButtonBase.WndProc(Message& m) bei System.Windows.Forms