Hi Cody,
Multi-file assemblies are simply assemblies that consist of more than one
file.
Multi-file assemblies are basically used when you want an inter-operability
between different languages,i.e,
maybe some of your programmers only know VB, maybe you need to interop with
some old C/C++ code.
Now you could put each language in its own assembly, but then you get stuck
with a poor organization model.
So,you can have multi-file assemblies where each file may be for a different
language.
You can read up more on this on the following link:
[Multi-file Assemblies]
http://blogs.msdn.com/grantri/archiv...07/175745.aspx
The biggest advantage of using multi-file assemblies over multiple
assemblies was a more compact organization model.
But,now in the coming version of VB.NET,i.e,Whid bey,you can have a single
file assembly with, VB, C#, C++, and
even native code all in one file! Theoretically you can even link classic
static .LIBs into your brand new C# assembly.
So,multi-file assemblies are on their way out!
HTH
Mona
"cody" <de********@gmx .de> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
What are multi file assemblies good for?
What are the advantages of using multiple assemblies (A.DLL+B.DLL) vs. a
single multi file assembly (A.DLL+A.NETMOD ULE)?