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.
I was doing that, somewhat. I had one snk for each solution. I have several drive-rooted folders with hundreds of solutions for 4 different customers (and some for me). I could have put the snk files in one location and referenced them all from there, but that would complicate source control and copying the projects across machines. I’m very happy with having the snk pair and my Thawte certificate in the CSP store. It’s an eternal dependency to builds, but you prepare it once and forget. It also means the keys are out of sight and optionally password protected from export. Greg
