Create Multiple Assemblies from a Single .NET Framework Source File
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiah8egG_rk5xGrOKZJm9kiCmnYMCAIKLR9p4wXftQ0ZZMI2CFHBlseydtLaBVGyULJTEM8ez-eJeux1WUN_BmKixS2Cx6I-yv_SaqnTaTsTM2nP4tTFFTyyedF8T67ab4TNnuk2f0Gi3fKIO6uVmaQiRWrz7rcj8kOcAd2gLDFfEuejhDQak12FJ32eI6A/s1600/one-to-many-assemblies.png)
This article is a continuation of Set .NET Assembly File Version Info in Source Code . Here, we explore the use of Conditional Compilation to reinforce coherent versioning across multiple assemblies. By the way, with the help of compiler symbols and conditional statements, we can delineate the assemblies' codes from each other and pack them in a single source file. These code blocks will share the same header from where we initialize their version attributes. So, when there is a need to change the version or a piece of information, we will change it from one file. This solution is just an alternative to Visual Studio for project management, and I prefer it for simple use-case projects. Here is a simple example. We have two source files, which I will compile into a library and an application, respectively. Library.Launcher.cs using System; using System.Reflection; [assembly: AssemblyProduct("My Product")] [assembly: AssemblyInformationalVersion("0.4.0.12"