[Via Infoworld] Microsoft is offering an upgraded version of its ILMerge utility, which merges multiple .Net assemblies into a single assembly. ILMerge is available for download from the Microsoft Download Center.
ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly. ILMerge takes a set of input assemblies and merges them into one target assembly. The first assembly in the list of input assemblies is the primary assembly. When the primary assembly is an executable, then the target assembly is created as an executable with the same entry point as the primary assembly. Also, if the primary assembly has a strong name, and a .snk file is provided, then the target assembly is re-signed with the specified key so that it also has a strong name.
ILMerge is packaged as a console application. But all of its functionality is also available programmatically. While Visual Studio does not allow one to add an executable as a reference, the C# compiler does, so you can write a C# client that uses ILMerge as a library.
There are several options that control the behavior of ILMerge. See the documentation that comes with the tool for details.
Currently, ILMerge does not work on Rotor or Mono.
A couple of months ago I remember discussing on how to reduce the dependency coupling of objects. We had a look at a number of design patterns like Inversion of Control and Dependency Injection which are great ways to solve this issue. The September issue of the MSDN Magazine has a good article on dependency injection using .NET dependency injection frameworks like Spring.NET and Pico.NET.
While catching up after my holidays I came accross a great number of publications covering ASP.NET 2.0. An overview.
If you like to listen to geek talk, check out the ASP.NET Podcast Show #12 - Paul Glavich does the full Show and Interviews Greg Low. Download.