ocx

I would like to create an activeX control(OCX) in VB .net 2010 is it possible? I having a hard time determining how to make it because I only get a .dll file rather than a .ocx which can be seen in vb6. I hope you can answer my question. Are you asking how to create an "ActiveX" control specifically or are you asking how to create controls that can be used by other CLR based applications? To create an ActiveX control, see this link which walks you through the steps to do this: Creating an MFC ActiveX Control To create standard controls, you use a dll (class library) and can add as many

I have ocx created in VC++ If it is loaded statically it works fine but when I load it dynamically from assembly it gives exception . public Assembly assembly; public Form1() { InitializeComponent(); assembly = Assembly.LoadFile(Application.StartupPath + "\\abc.ocx"); } it gives following exception The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018) You'll have to perform a number of steps that are normally taken of automatically when you use the toolbox. First and foremost, you have to run the Aximp.exe utility to generate the .NET interop assemblies.

I am trying to register RichTx32.Ocx for an application I am working on in Access 2010 (File Format 2003 mdb). I have been updated to Windows 7 64 bit (from Windows XP SP3 32 bit) and can't get the ActiveX OCX to register. I have put the file in the system32 folder and get the following message: "The module "RICHTX32.OCX" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe" When I put the file in the SysWOW64 folder and run regsvr32 to that location, I get the following error message:

In an Excel 2003 VBA project I am using controls from MSCOMCTL.OCX. That is the VBA project has a reference to System32\MSCOMCTL.OCX. When I open that project in Excel 2003 on my 64-bit Windows 7 system, Excel automatically changes the reference to SysWOW64\MSCOMCTL.OCX (which is the correct location). However, when I send that project to my client who is using 32-bit Windows XP, the project complains during opening because SysWOW64\MSCOMCTL.OCX does not exist on his system. Here are the (unsatisfactory) solutions I came up with so far: Instruct the client to manually change the reference back

What happened to OCX's? Are they no longer possible to create with the latest tools? I need to create an ActiveX control that I can place in Word, PowerPoint and Excel documents. If I use VS.NET, I can only create a UserControl DLL with COM Interop, but I don't think I can add that using the "More Controls" toolbox of PowerPoint's Developer Tab. What would you do? Yes, you can still create them. But you can't create an OCX with a .NET language. Need to be unmanaged C++ (or VB). The DLLs with COM interop you can create in C# or VB.NET are just .NET objects that are invoked via CCW. You can

I've added an .ocx to the toolbox in VS. Two .dll's were created: Interop.NNN.dll, AxInterop.NNN.dll. What is each one? Are they both required? The AxFoo.dll assembly contains an automatically generated class that's derived from the System.Windows.Forms.AxHost control. It is pretty simple, it has methods, properties and events, the same ones you have available in the .ocx, that simply call the Foo.dll interop library. So, yes, you definitely need to deploy both assemblies. Interop.xxx.dll and AxInterop.xxx.dll are runtime callable wrappers (RCW) for a referenced COM and an ActiveX dll