On Thu, Oct 6, 2011 at 11:39 PM, Greg Keogh <[email protected]> wrote: > Folks, here’s a heads-up!**** > > ** ** > > I got sick of having hundreds of identical SNK files in projects > everywhere, so I ran a sn -i foo.snk MyContainer to put the key pair into > a container.**** > > ** ** > > As far as i can tell, there is no way in a C# VS2010 solution that you can > configure some settings to tell the projects to use the container. If anyone > knows this is wrong, urgently let me know ... because in the absence of any > formal configuration method I had to insert this line into the first > PropertyGroup of every csproj file:**** > > ** ** > > <KeyContainerName>MyContainer</KeyContainerName>**** > > ** ** > > Then I noticed that none of the outputs were signed. After some stuffing > around I found that you can’t have the line above at the same time as > <SignAssembly>true</SignAssembly> because they silently conflict and nothing > is signed. I then globally changed the latter to <SignAssembly/> and now the > signing is working from the container.**** > > ** ** > > How about having one foo.snk file at the top level of your solution, and all projects reference it? (..\..\foo.snk) That way, it's in your repository, and all devs are using the same one.
> -- > Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
