The trick is you can also add this attribute at assembly level (in AssemblyInfo.cs). If you specify [assembly: ComVisible(true)] (or don’t specify that at assembly level and so have the same effect by default) then all the public classes and interfaces and public methods thereof become COM-visible by default. You could just as well set … Read more
Found Answer…….!!!!!!! Officially Microsoft Office 2003 Interop is not supported on Windows server 2008 by Microsoft. But after a lot of permutations & combinations with the code and search, we came across one solution which works for our scenario. The solution is to plug the difference between the way Windows 2003 and 2008 maintains its … Read more
The easiest way (and Rob M will rant and rave about how this is wrong) is just to use SelfRegCost=1 on the File tag for the DLL. This is wrong, because we should be explicitly controlling the registration of the DLL, not allowing it just to run arbitrary code via DllRegisterServer. The theory being that … Read more
You can use the assembly binding failure logging feature – it needs to be enabled and then you can use the fusion log viewer to see the results http://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.110).aspx Not sure how you will get this onto your clients machines. When I first read this my first thought was given it seems most common on … Read more
If the library is already registered, you can perform the following steps to have Visual Studio generate an interop assembly for you: Open to your Visual Studio project. Right click on ‘References’ (right under the project in your Solution Explorer) and select ‘Add Reference’. Select the COM tab. (If you don’t see this, you have … Read more
First you have to install the wonderful pywin32 module. It provides COM support. You need to run the makepy utility. It is located at C:\…\Python26\Lib\site-packages\win32com\client. On Vista, it must be ran with admin rights. This utility will show all available COM objects. You can find yours and it will generate a python wrapper for this … Read more
You should use Heat (WIX 3.0) located in the bin directory of the version you are using. Have a look at this blog post, we use it here to register all our COM objects, by creating a wix fragment… something like heat file MyComExposedLibrary.dll -out MyComExposedLibrary.wxs After, reading your edit, I would create a basic … Read more
Yes, that’s possible. Especially in the case of .NET, you should not omit registering the type library because you cannot predict how the client code is going to use your server. They are not particularly common but there are two cases: When the client code calls your [ComVisible] method and the call crosses an apartment … Read more
To find the DLL, go to your 64-bit machine and open the registry. Find the key called HKEY_CLASSES_ROOT\CLSID\{681EF637-F129-4AE9-94BB-618937E3F6B6}\InprocServer32. This key will have the filename of the DLL as its default value. If you solved the problem on your 64-bit machine by recompiling your project for x86, then you’ll need to look in the 32-bit portion … Read more
Have you tried calling CoInitializeSecurity() with RPC_C_AUTHN_LEVEL_CALL instead of RPC_C_AUTHN_LEVEL_CONNECT? Usually when I create DCOM clients I create COSERVERINFO and pass to CoCreateInstanceEx() with security credentials, remembering to call CoSetProxyBlanket() on all interfaces.