'static library' in .net 2.0?

  • Thread starter Thread starter babylon
  • Start date Start date
B

babylon

I heard that it is possible to build a static library like .lib in .net
framework 2.0
so that the library can be integrated into the resultant .exe instead of
loading the library in .dll during load/run time..
is that true?

thank you

Action
 
If you have the source to the library, why not just Add existing item and
"Link to.." in the drop down open button.

I do that but yeah having static assemblies would be nice.
 
sometimes it don't work
e.g. when using embedded icons/bitmap
the namespace of the source will be changed so it breaks the source code..
 
http://www.developer.com/net/article.php/3099811

Starting with Whidbey, you will have static linking available to you. To
switch from a traditional reference to MSIL linking, simply:
a.. Change the library project so it produces a .netmodule file instead of
a .dll assembly
b.. Change the application project so it links in the .netmodule file
c.. Remove any reference to the .dll file and replace it with a reference
to the .netmodule file
 
Here they are talking about MSIL linking through netmodules, a feature not
available in VS 2002/2003, but which will be in VS 2004.
However, this has nothing to do with static linking, netmodules are not new
they existed from the first incarnation of .NET, but you have to use command
line build tools (nmake etc...) to produce multimodule assemblies.
Check the msdn documentation if you need more info on .netmodules.

Willy.
 
Back
Top