search

ronysebastian / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

Assemblies do not have strong names #164

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
From the windows sdk folder %program files%/Microsoft sdks/windows/v[6-7].0A 
run the command sn -v {path to direct project assembly}

What is the expected output? What do you see instead?
Expected: The assembly is valid, Actual: The assembly is not strongly named

Please provide any additional information below.
It's just a few lines in MSBuild to sign the assemblies or you can do it 
manually from the properties of all the .csproj files. We are getting the 
"certified for Microsoft Sever 2008" certification for our product and a 
prerequisite is all assemblies must have a strong name. (All strong named 
assemblies can only reference other strong named assemblies, however, not 
strong name assemblies can reference strong named assemblies)

Original issue reported on code.google.com by Jeph....@gmail.com on 11 Oct 2011 at 4:43

GoogleCodeExporter commented 9 years ago 
Sorry, this should probably be listed as an Enhancement or Task. I would be 
willing to to make the changes if you make me a contributor.

Original comment by Jeph....@gmail.com on 11 Oct 2011 at 4:51

GoogleCodeExporter commented 9 years ago

Original comment by bgran...@harris.com on 18 Oct 2011 at 3:03