I have a messy situation wrapping a couple of 3rd party COM components. Actually it\'s one COM component and several .NET assemblies. The .NET assemblies in turn depend on the same 3rd party\'s intern
I am a c# developer currently working on some legacy c++ com components. I am trying to add activation context api code to the com components in order to call other com components without registration
I am using Activation Context API in a .开发者_StackOverflow中文版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
I have a Registration-Free COM component I developed that is working fine on target machines without needing to register the component.It is in a dll that has tlb embedded, and an RT_MANIFEST resource
I have a unmanaged C++/ATL in-process COM object (in Unmanaged.dll) that I\'m trying to use from a managed C# DLL (Managed.dll).However, I want I want to use registration free COM.I have it down to th
I\'m trying to deploy an .NET application with a custom COM component through ClickOnce. Unfortunately the application does not work with manifests generated by Visual Studio to use the COM component
I have perhaps a silly question: We have a VC++ COM DLL (developed internally) and we have ported our main app to C# and used COM Interop, reg-free to access the COM dll. Everything works just fine w
I\'ve built a COM client application that uses two COM server dlls; I want this application to run without COM registration - ie: winsxs / .manifests
I\'m trying to use a 3rd party COM DLL (I don\'t believe its a .NET component) from a .NET service without registering the COM DLL but I\'m having no luck so far.
I have some .NET code I use from VB6 code.I have always developed this on an XP machine by crea开发者_JAVA技巧ting a VB6.exe.manifest file that listed the dependent .NET assemblies.
加载中,请稍侯......