regfreecom

Is it possible to use an ocx (ActiveX Control) on a winform (probably adding it programatically) without first having the ocx registered with regsrv32? What I'm trying to achieve is to enable xcopy installation. I've had the "AxInterop. .dll" and "Interop. .dll" file generated from my dev machine. I've seen the possibility of calling a COM dll without first registering it ( ProSysLib , according to the author, but I haven't tested it yet), since ocx is also COM based, thus I assume that there must be some way to do that as well. Yes, this can be done. You must assume your application will only

Windows allows use of a COM object without having to register the COM dll . The mechanism is to include a " dependent assembly " in the application's manifest: MyProgram.exe.manifest <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity type="win32" name="myapp.exe" version="1.2.3.4" /> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Contoso.Frobber" version="5.1.81.4" /> </dependentAssembly> </dependency> </assembly> And then your folder contains: MyProgram.exe MyProgram.exe

I am trying to access a VB.NET DLL (.NET FX 4.0) from a VB6 client in a reg-free scenario. I tried to follow the example from http://msdn.microsoft.com/en-us/library/ms973915.aspx , but with no success. I downloaded (link in the article) the sources and compiled, no success (error message: Run-time error '-2146234341 (8013101b)': Automation error"). Running from VB6 IDE using registered VB.NET DLL works. I tried other examples where the .NET DLL is created as a COM Class (using "COM Class" template from VS2010), with manifest for referenced DLL embedded or not, but nothing worked for me. Can

TL;DR Do all registry entries produced by regsvr32 need to be present in a SxS reg-free-COM manifest and vice versa? I'm trying to get registration free COM going for a third party component. Reading up on the subject, I find that there are several elements mentioned, that can be put into a manifest: From the docs , we can add the following tags to a manifest to describe a COM component: assemblyIdentity - which really just describes the "abstract assembly " as far as I can tell comClass - describes the COM class (IID Interface). It would appear, this is always needed. typelib - when?

Can any one tell me how to convert an legacy application which is vb6 ( COM dll's ocx and exes) to use Regfree COM . I tried opening the dlls in visual studio and created manifest file, but some of the dlls it is giving error. Is there any tools out there which will help me to do this process? I tried a tool from codeproject which is called regsvr42, which is not creating the manifest fully. I used tools like PE explorer where I get all the typelib information , but converting them into manifest files is too difficult. We have started migrating that to .NET, for some months we have to deploy