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
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
KPM build and use windows explorer check the generated dll property.
Actual:
Defined assembly info are not shown in windows explorer property page details tab.
From: David Fowler
More like our use of roslyn, might need to specify something that isn't being specified right now.
From: Levi Broderick
The Explorer "Details" view is populated by the Win32 module manifest baked into the assembly. Normally csc.exe generates this Win32 manifest at compile time based on the assembly-level attributes it encounters. Perhaps Roslyn isn't doing this for some reason?
The text was updated successfully, but these errors were encountered:
It looks like the Roslyn doesn't generate the manifest during assembly emit based my experiment. If so, out builder needs to update the file properties on our own.
danroth27
changed the title
ProjectK dll property details tab does not show assembly info attribute
Dll property details tab does not show assembly info attribute
Jan 13, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[assembly: AssemblyTitle("testTitle")]
[assembly: AssemblyDescription("test Discription")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("test comany")]
[assembly: AssemblyProduct("test product")]
[assembly: AssemblyCopyright("test Copyright © .")]
[assembly: AssemblyTrademark("test trademark")]
[assembly: AssemblyCulture("")]
Actual:
Defined assembly info are not shown in windows explorer property page details tab.
From: David Fowler
More like our use of roslyn, might need to specify something that isn't being specified right now.
From: Levi Broderick
The Explorer "Details" view is populated by the Win32 module manifest baked into the assembly. Normally csc.exe generates this Win32 manifest at compile time based on the assembly-level attributes it encounters. Perhaps Roslyn isn't doing this for some reason?
The text was updated successfully, but these errors were encountered: