You searched for the word(s): userid:700805

More Search Options

RSS Available

• Re: Assembly generation failed -- Referenced assembly does not have a strong name

  Thanks Mark, I understand that the the 2 projects types are different and use different build models and that it's something to do with the new build model that is causing the "Web Application Project" to have problems with my unsigned 3rd party assembly. Maybe question 1 should have been 1. What difference in the build models causes the assembly generation failure in "Web Application Projects" and not in "Web Site Projects" when the web project is signed and references an unsigned assembly? I use

  Posted to VS 2005 Web Application Projects (Forum) by steven.miles on 1/5/2007

• Assembly generation failed -- Referenced assembly does not have a strong name

  Hi, I've attempted to migrate a VS2005 "Web Site Project" to "Web Application Project". I overcome all issues except 1. When i try to build my new project it compains that a referenced assembly isn't strong named. Unfortunatley this is a third party .NET assembly so it is not built as part of my solution. Both new and old web projects are instructed to be signed in the assemblyinfo.cs the old web site project compiles and publishes fine and the new one doesn't. I've read some pages that suggest i

  Posted to VS 2005 Web Application Projects (Forum) by steven.miles on 1/5/2007
  Filed under: Visual Studio 2005 SP1 Service Pack 1, VS 2005, ASP.NET, Compilation Error