Creating a COM component in .NET 5
-
Hi, I'm trying to create a simple COM component in .NET 5. I have gotten this far: * I have created an interface with the right attributes:
\[ComVisible(true)\] \[Guid("12345678-3e60-4c56-abcd-13d4098434f7")\] \[InterfaceType(ComInterfaceType.InterfaceIsIUnknown)\] public interface IConvertor { string ConvertPatient(string s); }* I have created a class that implements this interface:
\[ComVisible(true)\] //\[ClassInterface(ClassInterfaceType.None)\] public class Convertor : IConvertor { public Convertor() { } public string ConvertPatient(string s) { return "Hello, " + s; } }I tried with and without the ClassInterface and Guid attributes. * In the .csproj file I added these:
net5.0
true true x86I compiled for x86 and I got these files (and some more): xxx.comhost.dll xxx.dll The problem is that I don't manage to register this component. tlbexp xxx.InterOp.dll gives me this error:
Quote:
TlbExp : error TX0000 : Type library exporter encountered an error while processing 'hdmpcloud.ehealth.FhirTools.InterOp.Convertor, hdmpcloud.ehealth.FhirTools.InterOp'. Error: Type library exporter cannot load type 'hdmpcloud.ehealth.FhirTools.InterOp.Convertor' (error: Could not load file or assembly 'System.Runtime, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (Exception from HRESULT: 0x80070002)).
regasm /tlb xxx.InterOp.comhost.dll gives me
Quote:
RegAsm : error RA0000 : Failed to load 'C:\_projects\HDMP\hdmpcloud.ehealth.FhirTools\InterOp\hdmpcloud.ehealth.FhirTools.InterOp\bin\Debug\net5.0\hdmpcloud.ehealth.FhirTools.InterOp.comhost.dll' because it is not a valid .NET assembly
I want to call this compo
The file you're trying to register seems to have no relation to "Convertor"; at least as far as naming goes. And I would have picked a more unique name than "Convertor".
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
The file you're trying to register seems to have no relation to "Convertor"; at least as far as naming goes. And I would have picked a more unique name than "Convertor".
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Hi Gerry, Thanks for the tips. But I'm afraid that changing the names will not help in registering the COM component. If you have tips for that I'll be glad to hear them. Thanks, Gaston
Check out my blog at http://msdev.pro/
-
Hi Gerry, Thanks for the tips. But I'm afraid that changing the names will not help in registering the COM component. If you have tips for that I'll be glad to hear them. Thanks, Gaston
Check out my blog at http://msdev.pro/
Maybe this will help:
Quote:
I used regasm.exe /tlb /codebase to register it
[[Solved] .net Call C# dll from Delphi - Code Redirect](https://coderedirect.com/questions/188647/call-c-sharp-dll-from-delphi) [dll - RegAsm - When is the /codebase option applicable? - Stack Overflow](https://stackoverflow.com/questions/23939699/regasm-when-is-the-codebase-option-applicable)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
Maybe this will help:
Quote:
I used regasm.exe /tlb /codebase to register it
[[Solved] .net Call C# dll from Delphi - Code Redirect](https://coderedirect.com/questions/188647/call-c-sharp-dll-from-delphi) [dll - RegAsm - When is the /codebase option applicable? - Stack Overflow](https://stackoverflow.com/questions/23939699/regasm-when-is-the-codebase-option-applicable)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Thanks for the link! Unfortunately it doesn't help. It seems that regasm doesn't recognize .NET 5 assemblies. Regsvr32 does, and it registers the component / interface / library, but no TLB is generated. That makes it virtually useless. From [Exposing .NET Core components to COM | Microsoft Docs](https://docs.microsoft.com/en-us/dotnet/core/native-interop/expose-components-to-com) :
Quote:
Unlike in .NET Framework, there is no support in .NET Core or .NET 5+ for generating a COM Type Library (TLB) from a .NET assembly. The guidance is to either manually write an IDL file or a C/C++ header for the native declarations of the COM interfaces.
So now I'm investigating how to create / compile / use the correct IDL file. Should anyone have some good pointers for that, let me know :-) Thanks, Gaston
Check out my blog at http://msdev.pro/
-
Thanks for the link! Unfortunately it doesn't help. It seems that regasm doesn't recognize .NET 5 assemblies. Regsvr32 does, and it registers the component / interface / library, but no TLB is generated. That makes it virtually useless. From [Exposing .NET Core components to COM | Microsoft Docs](https://docs.microsoft.com/en-us/dotnet/core/native-interop/expose-components-to-com) :
Quote:
Unlike in .NET Framework, there is no support in .NET Core or .NET 5+ for generating a COM Type Library (TLB) from a .NET assembly. The guidance is to either manually write an IDL file or a C/C++ header for the native declarations of the COM interfaces.
So now I'm investigating how to create / compile / use the correct IDL file. Should anyone have some good pointers for that, let me know :-) Thanks, Gaston
Check out my blog at http://msdev.pro/
I'm for the path of least resistance. Unless you need "real time", I would've windows message queues; at least to start with; which might be real enough. [Easily Implement Message Queue Communications Protocols In Your Windows Applications](https://blogs.embarcadero.com/easily-implement-message-queue-communications-protocols-in-your-windows-applications/)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
I'm for the path of least resistance. Unless you need "real time", I would've windows message queues; at least to start with; which might be real enough. [Easily Implement Message Queue Communications Protocols In Your Windows Applications](https://blogs.embarcadero.com/easily-implement-message-queue-communications-protocols-in-your-windows-applications/)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Hi Gerry, I was under the assumption that creating a COM component would still be as easy under .NET 5 as under the previous versions. We don't need real time at all. This would be part of a conversion program, that will run on the client PCs (> 3000 clients, with all sorts of PCs and OS's). I wanted to avoid having to serialize objects on the Delphi side, and to deserialize them on the .NET side. I think that we will resort to creating a file (or a couple of files) in a folder, and when that is done running the conversion program on the client PC. That way we only have to install .NET 5 and the conversion program, which is even easier than using a queue. Thank you for thinking with me for solutions! I am going to do 1 more try, posting the same question on SO. Please don't be insulted ;-) If I find a solution I will post it here.
Check out my blog at http://msdev.pro/
-
Hi Gerry, I was under the assumption that creating a COM component would still be as easy under .NET 5 as under the previous versions. We don't need real time at all. This would be part of a conversion program, that will run on the client PCs (> 3000 clients, with all sorts of PCs and OS's). I wanted to avoid having to serialize objects on the Delphi side, and to deserialize them on the .NET side. I think that we will resort to creating a file (or a couple of files) in a folder, and when that is done running the conversion program on the client PC. That way we only have to install .NET 5 and the conversion program, which is even easier than using a queue. Thank you for thinking with me for solutions! I am going to do 1 more try, posting the same question on SO. Please don't be insulted ;-) If I find a solution I will post it here.
Check out my blog at http://msdev.pro/
Seems it's more of a "command and control" issue than a data transfer one. Lots of possible scenarios.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
Seems it's more of a "command and control" issue than a data transfer one. Lots of possible scenarios.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Indeed, we have thought of alternatives before going to the "COM road". But COM seemed the easiest in our case for a couple of reasons, hence the initial question here.
Check out my blog at http://msdev.pro/
-
Seems it's more of a "command and control" issue than a data transfer one. Lots of possible scenarios.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
According to the replies on SO this is a dead end indeed. We now are going to create classes in C# and in Delphi with all the same properties. We'll then serialize the Delphi classes to JSON, and deserialize them in C#. For this I'm writing a code generator that will use a DSL to describe the classes. It's a work-around, but at least we'll get the work done.
Check out my blog at http://msdev.pro/
-
According to the replies on SO this is a dead end indeed. We now are going to create classes in C# and in Delphi with all the same properties. We'll then serialize the Delphi classes to JSON, and deserialize them in C#. For this I'm writing a code generator that will use a DSL to describe the classes. It's a work-around, but at least we'll get the work done.
Check out my blog at http://msdev.pro/
-
That's the protocol; you still need a transport mechanism.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
This is for a conversion, so the Delphi side will serialize the objects in a folder, and the .NET part will deserialize it and handle it further. It is a One Shot operation, so no need for fancy stuff there.
Check out my blog at http://msdev.pro/
-
The file you're trying to register seems to have no relation to "Convertor"; at least as far as naming goes. And I would have picked a more unique name than "Convertor".
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
इस घटना में कि आपके पास वीज़ा है, आपको इसे खरीदारी के लिए उपयोग करना चाहिए। जिसके बाद आपको भी उतनी ही राशि का भुगतान करना होगा। यह मानते हुए कि आपको इस वीज़ा किस्त के एवज में एक पुरस्कार के रूप में कैशबैक भी मिलता है, तब, आप स्कोर को और अधिक लाभ देंगे। इस लेख में
आपको एक ऐसी एप्लीकेशन के बारे में बताया जा रहा है, जिसके जरिए अगर आप वीजा बिल का ध्यान रखते हैं तो आपको इसके परिणामस्वरूप कुछ कैशबैक भी मिलता है।
-
Maybe this will help:
Quote:
I used regasm.exe /tlb /codebase to register it
[[Solved] .net Call C# dll from Delphi - Code Redirect](https://coderedirect.com/questions/188647/call-c-sharp-dll-from-delphi) [dll - RegAsm - When is the /codebase option applicable? - Stack Overflow](https://stackoverflow.com/questions/23939699/regasm-when-is-the-codebase-option-applicable)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Yes thanks alot I got the help from . Full Stack User