typelib

问题 How to create a parameter of type PSafeArray? I take the following error from C# COM library: SafeArray with range 65262 transfered to the method that requires array with range 1 Delphi XE2 should call C# COM library procedure using Generated RIDL type-library with a parameter of type PSafeArray. Delphi XE2 code: function GetObjects: PSafeArray; var aObjects: Variant; begin aObjects := VarArrayCreate([0, 2], varVariant); aObjects[0] := ADOConnection.ConnectionObject; aObjects[1] :=

问题 I’m trying write client application to CANoe (application by Vector). I can fully control one application trough COM server objects but if i create a new application instance, gCanAppB, the original instance gCanAppA is closed. How can i tell to the COM Server, that open the new instance in new application window? My source code: Set gCanAppA = CreateObject( "CANoe.Application") Set gCanAppB = CreateObject( "CANoe.Application") gCanAppA.Open ("Easy.cfg") gCanAppA.CAPL.Compile gCanAppA

问题 I’m trying write client application to CANoe (application by Vector). I can fully control one application trough COM server objects but if i create a new application instance, gCanAppB, the original instance gCanAppA is closed. How can i tell to the COM Server, that open the new instance in new application window? My source code: Set gCanAppA = CreateObject( "CANoe.Application") Set gCanAppB = CreateObject( "CANoe.Application") gCanAppA.Open ("Easy.cfg") gCanAppA.CAPL.Compile gCanAppA

问题 I've seen several (not all) registry values like the followings, when trying to parse out the file path under the TypeLib registry key: HKEY_CLASS_ROOT\TypeLib\\{EE9CFA8C-F997-4221-BE2F-85A5F603218F}\1.0\0\win64(Defalt): C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesX64\Microsoft Office\Office16\OCHelper.dll\1 HKEY_CLASS_ROOT\TypeLib\\{F9E34568-0298-46D3-B9C4-19AFB415CBA8}\1.0\0\win32(Default): C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\mswebprj.dll\5

问题 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 have a native C++ DLL, and I want to import a C# DLL and use some of its functions (for example connecting to a database). Now I have read that you can turn the DLL into a TLB COM file, and I have done that no problems. My problem lies with the C++. To call that TLB file I need to set CLR support. I use themida to help secure all my DLL's as well as PEC. They do not support .net DLL's and when I enable CLR the programs recognize it as a .net DLL. Is there anyway to call a c# function inside

问题 I am maintaining a VS2010 project which has a number of cross-referenced COM libraries. I am trying to configure the project in such a way that it is buildable from a random workstation which has VS2010 installed. The workstation could be both 32 and 64 bit, so if I configure project to "register output", the build will fail to build on 32-bit machine, since 64-bit DLL will not be possible to load to call DllRegisterServer. Here is an example: Typelib from project B references typelib from

问题 I am maintaining a VS2010 project which has a number of cross-referenced COM libraries. I am trying to configure the project in such a way that it is buildable from a random workstation which has VS2010 installed. The workstation could be both 32 and 64 bit, so if I configure project to "register output", the build will fail to build on 32-bit machine, since 64-bit DLL will not be possible to load to call DllRegisterServer. Here is an example: Typelib from project B references typelib from

问题 I am maintaining a VS2010 project which has a number of cross-referenced COM libraries. I am trying to configure the project in such a way that it is buildable from a random workstation which has VS2010 installed. The workstation could be both 32 and 64 bit, so if I configure project to "register output", the build will fail to build on 32-bit machine, since 64-bit DLL will not be possible to load to call DllRegisterServer. Here is an example: Typelib from project B references typelib from

问题 I am working with two ATL-based COM projects. The both implement DllRegisterServer as just STDAPI DllRegisterServer(void) { // registers object, typelib and all interfaces in typelib return _Module.RegisterServer(TRUE); } which ends up calling ::RegisterTypeLib(pTypeLib, bstrPath, szDir); in atlbase.h:6516. But for some reason this call makes one of the projects create HKEY_CLASSES_ROOT\TypeLib\<guid>\<version>\0\win64 when registered using regsvr32.exe on Windows 7 32 bit. The other project