Shared Assembly Info refers to the assembly attributes that should be the same across all projects in the solution, such as AssemblyCompanyAttribute.
--- title: Shared Assembly Info in Visual Studio Projects author: Jeremy Jameson date: April 3, 2009 source: http://www.technologytoolbox.com/blog/jjameson/archive/2009/04/03/shared-assembly-info-in-visual-studio-projects.aspx --- > **Note** > > This post originally appeared on my MSDN blog: > > Since [ I no longer work for Microsoft], I have copied it here in case that blog ever goes away. Yesterday I introduced the concept of [linked files in Visual Studio solutions] with a follow-up on my recommendation for [configuring a custom dictionary] to eliminate CA1704 code analysis warnings. Another practical application of linked files is what I refer to as "shared assembly info" -- referring to the assembly attributes that should be the same across all projects in the solution, such as [AssemblyCompanyAttribute]. To implement this, create a file in the solution folder named `SharedAssemblyInfo.cs` and then add a link in each project to SharedAssemblyInfo.cs. You can also move the linked `SharedAssemblyInfo.cs` into the Properties folder so that it sits side-by-side with the `AssemblyInfo.cs` that is specific to each project in the solution, as shown below. ![Linked SharedAssemblyInfo.cs files in a Visual Studio solution] **Figure 1:** Linked `SharedAssemblyInfo.cs` files in a Visual Studio solution I recommend placing the following assembly attributes in `SharedAssemblyInfo.cs` (and, of course, removing them as necessary from the project-specific `AssemblyInfo.cs` files): - AssemblyCompany - AssemblyProduct - AssemblyCopyright - AssemblyTrademark - AssemblyConfiguration - AssemblyDescription - CLSCompliant - ComVisible - AssemblyVersion - AssemblyInformationalVersion The `AssemblyInfo.cs` files typically have the following assembly attributes: - AssemblyTitle - AssemblyCulture - Guid Here is a sample **SharedAssemblyInfo.cs** file: ```cs using System; using System.Reflection; using System.Runtime.CompilerServices; using System.Runtime.InteropServices; // General Information about an assembly is controlled through the following // set of attributes. Change these attribute values to modify the information // associated with an assembly. [assembly: AssemblyCompany("Fabrikam Technologies")] [assembly: AssemblyProduct("Demo")] [assembly: AssemblyCopyright("Copyright ? Fabrikam Technologies 2009")] [assembly: AssemblyTrademark("")] // Make it easy to distinguish Debug and Release (i.e. Retail) builds; // for example, through the file properties window. #if DEBUG [assembly: AssemblyConfiguration("Debug")] [assembly: AssemblyDescription("Flavor=Debug")] // a.k.a. "Comments" #else [assembly: AssemblyConfiguration("Retail")] [assembly: AssemblyDescription("Flavor=Retail")] // a.k.a. "Comments" #endif [assembly: CLSCompliant(true)] // Setting ComVisible to false makes the types in this assembly not visible // to COM components. If you need to access a type in this assembly from // COM, set the ComVisible attribute to true on that type. [assembly: ComVisible(false)] // Note that the assembly version does not get incremented for every build // to avoid problems with assembly binding (or requiring a policy or // <bindingredirect> in the config file). // // The AssemblyFileVersionAttribute is incremented with every build in order // to distinguish one build from another. AssemblyFileVersion is specified // in AssemblyVersionInfo.cs so that it can be easily incremented by the // automated build process. [assembly: AssemblyVersion("188.8.131.52")] // By default, the "Product version" shown in the file properties window is // the same as the value specified for AssemblyFileVersionAttribute. // Set AssemblyInformationalVersionAttribute to be the same as // AssemblyVersionAttribute so that the "Product version" in the file // properties window matches the version displayed in the GAC shell extension. [assembly: AssemblyInformationalVersion("184.108.40.206")] // a.k.a. "Product version" ``` Note how the [AssemblyConfigurationAttribute] and [AssemblyDescriptionAttribute] are set based on conditional compilation constants (in order to easily distinguish Debug and Release builds). Here is a sample **AssemblyInfo.cs** file: ```cs using System.Reflection; using System.Runtime.InteropServices; // Note: Shared assembly information is specified in SharedAssemblyInfo.cs // General Information about an assembly is controlled through the following // set of attributes. Change these attribute values to modify the information // associated with an assembly. [assembly: AssemblyTitle("Fabrikam.Demo.CoreServices")] [assembly: AssemblyCulture("")] // The following GUID is for the ID of the typelib if this project is exposed to COM [assembly: Guid("88d50bdd-34bc-414a-98d6-6fefe701d41b")] ``` In my [next post], I'll discuss assembly versioning in more detail. : http://www.technologytoolbox.com/blog/jjameson/archive/2011/09/02/last-day-with-microsoft.aspx : http://www.technologytoolbox.com/blog/jjameson/archive/2009/04/02/linked-files-in-visual-studio-solutions.aspx : http://www.technologytoolbox.com/blog/jjameson/archive/2009/04/02/ca1704-code-analysis-warning-and-using-custom-dictionaries-in-visual-studio.aspx : http://msdn.microsoft.com/en-us/library/system.reflection.assemblycompanyattribute.aspx : http://www.technologytoolbox.com/blog/images/www_technologytoolbox_com/blog/jjameson/7/o_Linked%20Files%20in%20Visual%20Studio%20Solutions.JPG : http://msdn.microsoft.com/en-us/library/system.reflection.assemblyconfigurationattribute.aspx : http://msdn.microsoft.com/en-us/library/system.reflection.assemblydescriptionattribute.aspx : http://www.technologytoolbox.com/blog/jjameson/archive/2009/04/03/best-practices-for-net-assembly-versioning.aspx