I have an ASP.NET web application developed in Visual Studio 2008, composed of 3 different projects (one for UI, one of BO and the third for DAL).
How can I generate a single assembly file which holds all 3? Now it's generating 3 DLLS each for each project in the solution.
Visual Studio extension that allows adding multiple existing projects into the solution. Optionally creates the solution folder structure reflecting to the physical hierarchy on disk. See the change log for changes and road map.
To build or rebuild a single project In Solution Explorer, choose or open the project. On the menu bar, choose Build, and then choose either Build ProjectName or Rebuild ProjectName. Choose Build ProjectName to build only those project components that have changed since the most recent build.
For each of your projects create a netmodule or an assembly and compile/merge them all into a single assembly.
First alternative. This was proposed by Jay R. Wren:
This is a cute hack, but with the CSC and VBC both supporting the
/target:module
and/addmodule
options, you could actually do this without ILMerge just by using a shell script or make file.Visual Studio doesn't support the "netmodule" type, but MSBuild does.
Add the VB project to your solution. Unload the project and edit the project file.
Change OutputType to module:
<OutputType>module</OutputType>
Instead of adding a reference to the desired project, we add a module. Sadly, again VStudio fails here, but MSBUILD works just fine. Unload the project and edit the project file. Add an item group with AddModules include directives.
<ItemGroup><AddModules Include="..\VbXml\bin\Debug\VbXml.netmodule" /></ItemGroup>
This will tell msbuild to tell CSC to use
/addmodule
directives, just like the Reference Item Group which Studio does manage.
Major Drawback: No Visual Studio Intellisense for the added module. We already have references, it is too bad we don't have modules.[UPDATE: As @Ark-kun pointed out elsewhere, Visual Studio can reference.netmodule
projects and have Intellisense. Just add the project reference BEFORE changing the output type.]SharpDevelop has the first step, but the second step, an "Add Module" gui has been open as a low priority item since SD 2.0.
Second way. This great article (by Scott Hanselman) describes how to megre assemblies automatically if you're using Visual Studio. It does give you IntelliSense support , unlike the first alternative.
Third way. Do it manually with scs.
Example how to create several modules and link theme into a single dll:
csc /t:module RarelyUsedTypes.cs
csc /out:AllTypes.dll /t:library /addmodule:RarelyUsedTypes.netmodule AllTypes.cs
For more information see Richter's book CLR via C#.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With