Surprisingly, there are quite some changes between Beta 2 and RC1, which caused my Beta2 project failed to compile in RC1.
Here is one that puzzled me, "Unable to find manifest signing certificate in the certificate store". I didn't sign my project in Beta2, and it didn't give me an error. So now in RC1, I have to sign my project It seems even if I uncheck the item in property page, as soon as I hit the publish, it will roll back to request the signing.
Migrate to VS2005 RC1
Hot Topic
- Line numbering in a Richtextbox
- Check Boxes and Tree view
- Closing Parent & Child Form Simultaneously.
- Data Search
- Databound listbox not updating
- Windows User Control :: Help
- Control sizes shink after opened from saved xml for .net 2003
- Has anyone changed IssuVision?
- net check before opening the form
- Override forecolor in textbox.enabled = false on windows form
Windows Forms
- Casting EventArgs object to KeyEventArgs - is it possible?
- Error Massage after Deploying application
- Problems with a Control
- Validating / Refresh Problems
- Keyboard shortcut for marking the whole text of a textbox?
- UI Design: When do you save?
- troubleshooting AppUpdater
- get info from a switch statement
- Delete multiple directory in file system
- Can I work on .NET 2.0 with VS2003?
Migrate to VS2005 RC1
Slappie
"unable to find manifest signing certificate" issue. If you "published" with the beta2 product your application this automatically creates a certificate and signs the click once manifest with it. If you then move your project to a different machine or "clean" off your machine between beta2 and RC1 and the again opened this same project it would be looking for that certiciate again to sign with. If you do not have the "old" certificate around to allow you to re-use it then you will have to create/get another one to use on the Signing page of the VS Project Designer (get to it via project|properties). One issue to be aware of is that if you are going to "republish" to the same location as the same app you will likely not be able to take advantage of the CO publishing auto-update from the beta2 to RC app since the identity will have changed due to the new certificate.
Hope this helps.
Robert Schoen (MS Visual Basic QA)
Netmaker
My project was developed and deployed on Beta2. So on a client machine, there is already Beta2 Framework. Without removing that, I tried to run the newly published version under RC1 through clickonce, and it failed (of course ! ). But then after I manually remove the Beta2 framework from the client, and use the run button to download and install the pre-requisite, it still fails. What I found is that the then installed framework is still beta2 version (50215), instead of the RC1 version (50727).
What's going on here