VS 2010, win server 2003, .Net 3.5 solution, which were migurated from .Net 1.1
All projects in solution are Delay signed. The soluton can be build successfully for
Since I'm not able to comment on the only answer to this I wanted to make sure that other users that came upon this answer as I did do not make the same mistakes other may have. According to the MSDN documentation for the strong naming utility, using the Vr(signature skipping) switch can cause malicious assemblies to load and should only be used in DEVELOPMENT not deployment.
http://msdn.microsoft.com/en-us/library/k5b5tt23(v=vs.80).aspx