Build Failed - assembly needs to be signed with a strong nam
maitpg1
Posts: 4
Why does v5 require a strong name to enable 'resource compression and encryption', 'error reporting', or 'string compression and encryption'? This was not a requirement in v4.2.
I can't give my assembly a strong name because it uses references that I don't own and can't assign strong names to.
I can't give my assembly a strong name because it uses references that I don't own and can't assign strong names to.
Comments
Darn developers... always think they know what's best.
Cheers,
Developer,
Red Gate .NET Tools