What is the practical use of the AssemblyTitle
attribute? MSDN says that it specifies a description for an assembly and that the assembly title is a friendly name which can include spaces.
Visual Studio asks for the assembly name in the properties window of the project along with the default namespace. There is an AssemblyName
attribute but it describes an assembly's unique identity in full (i.e., culture, etc.). I don't see how AssemblyTitle
differs from AssemblyProduct
.
I used the IL Disassembler to see how Microsoft uses AssemblyTitle
. I discovered that in mscorlib.dll, AssemblyTitle
, AssemblyProduct
and AssemblyDefaultAlias
are all set to "mscorlib.dll"
.
In conclusion, what I really would like to see are practical examples of the use of AssemblyTitle
.
Your Product can comprise of several assemblies.
All of the assemblies will have a single product name and individual assemblies will have their own titles.
AssemblyProduct = "MyProduct"
AssemblyTitle = "MyProduct.Utilities"
and for another assembly
AssemblyTitle = "MyProduct.Security"
the assembly title is also used in the explorer file properties etc.
File > Properties > Details
tabThe
AssemblyTitle
also appears as an application's name in the task manager (Windows 10), e.g. in the "Processes" tab or the "Fewer details" view.[AssemblyTitle] is a pretty big deal, it is directly visible when you right-click on the assembly and use Properties + Details.
An example to make it more visible. Let's start with this AssemblyInfo.cs file:
And look at the properties of the file:
Some annotations to this:
It is quirky, the Windows group and DevDiv didn't always work together well.