regfreecom

问题 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 -

问题 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

问题 I want to put my dependent files in the app directory. I seem to remember that you can force VB6 to use the files in the local directory only. Any hints? 回答1: You may also want to try setting up Reg-Free COM for your project. There's a freeware called Make My Manifest that will do most of the work for you EDIT The MMM website is down. I see here that the author was having trouble with their hosting and has provided another location to get Make My Manifest - download it here. 回答2: Placing

问题 I have some applications (some native, some .NET) which use manifest files so that they can be deployed in complete isolation, without requiring any global COM registration. For example, the dependency on the dbgrid32.ocx com server is declared as follows in the myapp.exe.manifest file which sits in the same folder as myapp.exe: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity type="win32" name=

问题 I have some applications (some native, some .NET) which use manifest files so that they can be deployed in complete isolation, without requiring any global COM registration. For example, the dependency on the dbgrid32.ocx com server is declared as follows in the myapp.exe.manifest file which sits in the same folder as myapp.exe: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity type="win32" name=

问题 I would like to create an instance of an ActiveX control. Given the .ocx file and interface definitions in C#, how can I do this? I don't mean the usual way of adding a reference to the project because I want to avoid the need for registering the control globally on the target system. 回答1: This looks like you should check into Registration-free COM. Beware that this does not work on older systems IIRC. For some details/samples etc. see: http://msdn.microsoft.com/en-us/library/fh1h056h.aspx

问题 I'm trying to use COM functions exposed by an EXE. I've created a C# project using Visual Studio 2010 (on a windows7/x64 machine) and added the reference to that EXE, then set the Isolated flag to true. When I build the solution, I get errors for each of the classes that it exposes. Problem isolating COM reference 'FNCClient11Lib': Registry key 'HKEY_CURRENT_USER\SOFTWARE\CLASSES\CLSID{e49b30c9-6d7e-48f5-91da-f2f0414c6a13}\InProcServer32' is missing value '(Default)'. These entries don't

问题 I want to use reg-free com so that I don't have to register my legacy com component. However, I would like to be able to put the com dll in a location which is not in or below the directory of the client exe, e.g. ....\lib. I'm not able to do this in the server manifest file as it doesn't allow relative or absolute paths. Does anyone know if there is a way round this? UPDATE: I only found relative paths to work on XP. However, I can use absolute paths on Windows Server 2008 using the

问题 I am using Activation Context API in a .Net client running in a location A to load a COM component reg-free in location B (which is completely different location to A, not a sibling/descendent etc. on the same machine) on WS2008 by passing in location B in the ACTCTX and it works fine. However, I now need to do the same thing with another COM dll which in turn has dependencies on a couple of .Net COM assemblies which live in completely different locations. I have added the dependent .Net

问题 Let's say I'm developing an application that installs COM component and installer registers them. This works great. Now the software is required to run from a memory stick. How can I register my libraries runtime and make sure, that the registry is cleaned up after running the application? 回答1: Are you always running on XP or later? Don't bother. Use "registration free COM". Essentially what you do is create a manifest file for the COM component so the Windows loader know what its