error MSB3323: Unable to find manifest signing certificate in the certificate store.
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.
[1259 byte] By [
bxs122] at [2008-1-7]
I got the same problem but I was tring to strong name my application. I was able to solve the problem by opening the XXX.csproj file in a text editor (notepad.exe) and remove the following tags from the XML.
<ManifestCertificateThumbprint>...</ManifestCertificateThumbprint>
<ManifestKeyFile>...</ManifestKeyFile>
<GenerateManifests>...</GenerateManifests>
<SignManifests>...</SignManifests>
It seem that someone (another member of my team) was playing with the OneClick stuff, but didn't check in the strong name key files he used. But did check in the project file.
Then when I created the new strong name key file and signed the EXE, something was out-of-sync with the above tags in the probject file and the new key file.
Removing these tags may be a bad thing (someone from MS will need to comment) but it worked for me.
I use strong keys for strong naming, and I use ClickOnce.
I got this error when I moved my project to another computer...
I tried unchecking the "Sign ClickOnce Manifests", but did not work.
I had to give a new "Valid" certificate first, and then uncheck the box...
It seems to me that when you uncheck that box, the project file is not updated accordingly... The certificate definition is still in there, and the build complains about it .
Any comments? Are my manifests really not being signed when I decide to NOT TO sign them anymore?
"... select a valid key there, or create a new one..."
wich key, I don't see any, pls be more specific, you helped me a lot so far!
Ok, I had a "good luck" and was able to solve the problem with the specified error message
Thanks for the help there, Mr. Bungle.
Mr. Bungle wrote: