Why do you ship the RV .NET component in two DLLs (TIBCO.Rendezvous.dll and TIBCO.Rendezvous.netmodule)?What is the significance of the TIBCO.Rendezvous.netmodule that is shipped along with the TIBCO.Rendezvous.dll?
Article ID: KB0087133
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
The need of the .NET module comes from a limitation of the C# language that does not allow the use of Cdecl calling convention for callbacks.
This is a C# limitation and not a .NET limitation as the CLR allows that. To solve this problem we provide the callback signatures in a separate module that contains callback definitions with Cdecl calling convention. It has to be a separate module since the .NET Disassembler contains a defect (reported to Microsoft) in the reassembled code. As .NET is not able to merge codes from different languages we have to provide two parts for our distribution: the main DLL and the .NET module. .NET module is part of .NET, and even supported by the C# compiler.
These are just not supported by Microsoft Visual Studio .NET. Once Microsoft supports this feature in Visual Studio we can modify it.
Issue/Introduction
Feedback
