tlbimp

问题 I'm trying to build an application that is strongly named. It is referencing a COM interop library that I add via the Add References dialog. It's been a while, but I seem to recall that in older versions of visual studio, there was a project setting for Wrapper Assembly Key File . I can't seem to find it in Visual Studio 2008? 回答1: I came across your post looking for the same thing, but found a different route on my own to get around the issue of strong naming a COM Interop referenced

问题 I need to regenerate the interop.dll from a type-library. Therefore I fired up TlbImp.exe" foo.tlb /out:interop.dll But in contrast to the original interop.dll , I found out with the object browser (see below) void SetNodeArr(int Size, FOO_NODE[] pArray) // original interop.dll that the open array for the method-parameter for SetNodeArr is lost: void SetNodeArr(int Size, ref FOO_NODE pArray) // regenrated interop.dll I've tried some of the options of TlbImp.exe, but with no luck. Q What tweak

问题 Observe this most trivial IDL file: import "unknwn.idl"; typedef struct _MyStruct { DWORD len; [size_is(len)] BYTE *buffer; } MyStruct; [ object, uuid(903C11E8-46A0-4E6E-B54C-6619B6A42CCB), pointer_default(unique) ] interface IMyIntf : IUnknown { [local] HRESULT Func([in] MyStruct *pObj); }; [ uuid(BAC6289C-503C-4ADD-B27A-4F22D726C109), version(1.0), ] library Lib { importlib("stdole2.tlb"); [ uuid(76D40083-C27F-45FB-88DC-C3E7DF9B5988) ] coclass MyClass { [default] interface IMyIntf; }; };

问题 I am writing a C# application which has several COM references. When I attempt to build it I get the following error for some of them: c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(1418,9): error MSB3303: Could not resolve COM reference "70850f66-869f-44a0-88e7-b0460a7e3bf3" version 0.1. The type library importer encountered an error during type verification. Try importing without class members. The application is still built and runs successfully. What does this error

问题 I am attempting to create a C# inproc server for sbtsv.idl (it is included with the Windows 8 SDK). Almost every instructions I find tell you to use MIDL to create a .tlb file then tlbimport to create the proxy dll. However, if the IDL does not include a library section no .tlb file will be generated, and sbtsv.idl does not include a library section. I tried creating my own IDL file that declared the interface I wanted to create inside a library #include "C:\Program Files (x86)\Microsoft SDKs

问题 We have a Visual Studio solution with about 90 projects. Most of them are built to DLL files, some are written in C++, others in C#. The projects communicate with each other via COM. We use tlbexp to generate TLB files of some C# projects (the ones that are referenced in C++ projects). And we use tlbimp to generate interop DLLs of the C++ projects. I did not completely dig into the topic, but I think, the interop files just define the interfaces of the C++ classes, to make them usable from

问题 I have a tlb file from a third party library. There are many versions of this library, however the functions that I use within the tlb are constant i.e. do not change from one version to the next. I have added the tlb file to the project as a COM Reference. I can successfully build and call the functions from the third party library. When I deploy my application, I cannot guarantee that the user will have the same version of the third party installed on their PC as me. When this scenario

问题 I made a class in C# that I am exposing to COM. I can register it just fine using RegAsm.exe. I would like to test it before I send it off, but using TlbImp.exe gives me an error of "Type libaray was exported from a CLR assembly and cannot be re-imported as a CLR assemply." What is a good way to test this? 回答1: You can create a VB macros in word\excel\etc: Dim obj As Object Set obj = CreateObject("progid here") Call obj.SomeMethodForTest() 回答2: Use PowerShell: $myObj = new-object -comObject

问题 I wrote a C# program and library that allow a user to more easily use a particular proprietary simulator's COM interface. Currently I have to build and distribute a different version of the C# library for each version of the simulator I wish to support. The company that develops the simulator regularly releases new versions, and each new version gets an incremented major version number. As far as I can tell, there is no change to the COM interface between versions (yet) so the calls and

问题 I have a method defined in IDL as follows : interface IMyFunc : IDispatch { [id(1), helpstring("method GetNextFunction")] HRESULT GetNextFunction( [in,out] long* lPos, [out, retval] BSTR* bstrName); } Using C++ I always implemented this as follows : STDMETHODIMP CMyFunc::GetNextFunction(long *nID, long *lPos, BSTR *bstrName) { if ( function to return ) { // setup return values; return S_OK; } else { // just exit return S_FALSE; } } Now I am implementing this in C# and have used tlbimp on the