You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIRC, Windows has some undocumented limit on the size of the VERSIONINFO resource. If a project sets a long Description for NuGet purposes, and .NET SDK starts copying that to AssemblyTitleAttribute, then the limit might be exceeded and Windows Explorer might not display any version information for that file, even though the VERSIONINFO resource was successfully written into the file.
In Windows 10, if you right-click a taskbar button, then the menu that pops up shows the AssemblyTitleAttribute, truncating it with an ellipsis if it is too long. I think this is another reason not to default AssemblyTitle from Description, which may be longer.
(The task bar caches the title and may keep showing the previous title even after you rebuild the assembly with a different title.)
Okay, I didn't know that. I still wonder, why Description is inferred from AssemblyTitle, but that's another discussion. In order to help my request, could AssemblyTitle be inferred from Title property, or is there also something against this?
Is your feature request related to a problem? Please describe.
In order to set the File description of an assembly file, one must set the
<AssemblyTitle>
.Describe the solution you'd like
Instead this could be infered from the package properties
<Description>
(that's what I actually expected) or<Title>
.Additional context
See also https://stackoverflow.com/questions/73736846/how-to-specify-assembly-description-in-an-sdk-style-project
The text was updated successfully, but these errors were encountered: