Managed dll interoperability?

Managed libraries written in say... C#, can be used in VB and the other way around, right? Like... without using System****ntime.Interoperability? With just a reference, right?

OMGHALP!

Yeah they can. Just compile the c#/VB code as a class library and then add the resulting dll as a reference to another project. That's all there is to it really.

So any .NET managed library can be used without interoperability problems in other .Net languages? Like a dll compiled from Visual Basic code will work fine in a C# project with just a reference, no special import function?

Originally Posted by t7ancients

Pretty much. I haven't tried out writing a class library that users pointers in C# and then importing it back into VB though.

To use pointers you need to mark your code with the "unsafe" keyword, right? I don't know anything about vb. Does it not have pointers or something?

Originally Posted by t7ancients

To use pointers you need to mark your code with the "unsafe" keyword, right? I don't know anything about vb. Does it not have pointers or something?

1: All .NET languages are interoperable to maximum extent.
2: If VB.NET has some equivalent of "unsafe", it will run, else not.

Managed dll interoperability?

Post a Reply

Tags for this Thread