I've been working on a .NET CF 2.0 project in VS2005 for a few weeks without any problems at all. Today, our IT staff switched our user accounts over to a new AD domain, and now when I try to build my project I get a strange error:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Common.targets(42,9): error MSB3482: SignTool reported an error 'Failed to sign obj\Debug\MobilePDA.exe. SignTool Error: ISignedCode::Sign returned error: 0x80092006
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Common.targets(42,9): error MSB3482: No provider was specified for the store or object.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Common.targets(42,9): error MSB3482: SignTool Error: An error occurred while attempting to sign: obj\Debug\MobilePDA.exe
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Common.targets(42,9): error MSB3482: '.
I tried "repairing" my VS2005 install, but no luck. Any ideas

Unable to sign assembly - 'No Provider Was Specified'
GBob
Well, I THOUGHT I'd fixed it. That took care of the problem signing the program during the build, and I can deploy the app to the emulator successfully, but I can't run it. If I try to run from the debugger, VS2005 gives me an error message box that says:
And if I try to start it directly on the emulator (from File Explorer), WM tells me:
I tried changing to the "Privlieged" certificate rather than the Unprivileged one, changing back to Unprivileged, etc. but there was no change. This is really puzzling (not to mention keeping me from getting any work done...)
Stevoie
Hi,
Does this certificate is installed on the device/emulator
If not, then
Thanks
Shabbar
Only One Tom
For whatever reason, under the project settings, on the Build pane, the "Platform target" drop-down had changed to Itanium instead of "All CPU". I changed this back, rebuilt the project, and things started working again.
I did not have to sign the project on the Devices pane.
EmilF
OK, I think I fixed it. I had to go into the "Devices" tab on the project properties, twiddle the Authenticode checkbox, and reselect the signing certificate.