Partitioning a code base through .NET
assemblies and Visual Studio projects
We put some myths to rest that promise a tenfold increase in speed of compilation.
This white book is aims to:
- Provide a list of DOs and DON’Ts when it comes to partitioning a code base into .NET assemblies and Visual Studio projects.
- Shed light on.NET code componentization and packaging.
- Suggest ways of organizing the development environment more effectively.
The aim of this is to increase the speed of .NET developer tools, including VS and C#/VB.NET compilers by merely rationalizing the development of a large code base. This will significantly increase productivity and decrease the maintenance cost of a .NET application.
This advice comes from years of real-world consulting and development work and has proved to be effective in several settings and on many occasions.
Table of Contents:
- Why create another .NET assembly?
- Common valid reasons to create an assembly
- Common invalid reasons to create an assembly
- Merging assemblies
- Reducing the number of assemblies
- Increase Visual Studio solution compilation performance
- Organize the development environment
- Organization of Assemblies
- Test assemblies organization
- VS Solutions files and Common build actions
Fill out the form to the right to download your copy