Cross Language Interoperability With C# .NET
The text of this article is not in this database — only its details are. Read it on the old site: Cross Language Interoperability With C# .NET
8 Comments
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
Anupam SinghPosted Jun 3, 2014, 1:55 AM
Nice article sir... very useful.
Praveen Raveendran PillaiPosted Jun 3, 2014, 12:47 AM
Nice article..Thanks for sharing..!!!
Vinod NairPosted Oct 9, 2013, 12:59 AM
Really great article Thanks
Naga SankarPosted Sep 10, 2013, 12:34 PM
Very nice article sir
Sam HobbsPosted May 12, 2013, 10:31 AM
Using unmanaged code, a single exe or single DLL can have code compiled from more than one language by statically linking the object files (the output of the compilers) together. So I could write a C++ program that calls code developed using COBOL, Pascal and/or Assembler. They could all be mixed together. Microsoft Visual Basic never worked like that but there are other Basic compilers that would. Using managed code, only one language can be used for each exe or DLL.
Vidya Vrat AgarwalPosted Apr 30, 2013, 5:49 PM
@Sam Hobbs, I am not very clear with your question. Are you asking, 1- If an exe can call code from C# class or dll and VB .NET class or dll? OR 2- Single dll can contain source code in C# and VB .NET language. Answer is - 1-Yes, 2- No
Sam HobbsPosted Apr 16, 2013, 6:04 PM
Is there a way that managed code can call programs written using a different language directly; in other words, if they are all in the same exe or the same DLL? Unmanaged code can do that but I see no way to do it using managed code. Therefore I think that managed code reduces cross-language interoperability in some significant ways.