error MSB3323: Unable to find manifest signing certificate in the certificate st

Problems began when I received the MSDN Final VS 2005 v8.0.50727.42 and uninstalled the RC build which I had worked with without issue and replaced it with the previously mentioned.

After four or so installs/uninstalls I got past the Invalid license data. Reinstall is required. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=162712&SiteID=1

I have tested C++ project builds for managed and unmanaged code and both work without a problem. My C# projects however fail to build, the error I get is:

------ Rebuild All started: Project: D And P, Configuration: Release Any CPU ------
C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Microsoft.Common.targets(1718,7): error MSB3323: Unable to find manifest signing certificate in the certificate store.
Done building project "D And P.csproj" -- FAILED.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

If anyone has any idea of what a next step is please let me know.

• 回复
• 引用

 

答案

• 2005年12月20日 10:36 Mr. Bungle

   
  

  18

  登录进行投票
  I got this when I renamed my C# project then tried to publish it. To solve, I went to the "Signing" tab of the project properties and unchecked "Sign the ClickOnce manifests". Good luck!
  • 回复
  • 引用

   
• 2008年5月6日 23:15 wazza1231

   
  

  2

  登录进行投票

  So i've read this thread a lot of times, but i've got the same problem like you had. If I unchecked the all the checkboxes from signin. .. I was allowed just to compile the program not to publish it.

  Now I've found somenthing,that solved my problem,and I think yours aswell.Go to Project -> project Proprietes -> Signin

  and then go to Create Test Certificate,and just give a simple password.And then enjoy publish it

   

  • 回复
  • 引用

   
• 2007年10月9日 21:10 Lu Zhao

   
  

  0

  登录进行投票

  I had the same problem by using ClickOnce, but after I deleted all the compiled dll's in the bin and debug folders, it's working. Hope this helps.

  • 回复
  • 引用

   
• 2010年3月10日 17:21 me.name.first is set to Joe

   
  

  0

  登录进行投票
  There are a lot of replies here.   My solution was similiar, but I'll state it here in case it will help anyone else.
  
  The "project" I inherited was targetting a CE Device.   Although I unchecked / checked / created / removed / unchecked the "Sign the Assembly" box under the "signing" tab in the project properties.   That did not resolve it.
  
  Under the "Devices" tab in project properties, another box was checked --
  In the "Authenticode Signing" section, the "Sign the Project Output with this Certificate" box was checked, but no ceritifacte was listed.
  
  After unchecking that box, I was able to build the project.