Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Lost passwort for signed assembly + ClickOnce...
 

Lost passwort for signed assembly + ClickOnce...

A while ago I wrote a C# application, signed the assembly (strong name) and deployed it via ClickOnce (also signed).

Later I moved the whole Visual Studio project to another machine. Now I have to do some changes in the source code and if I try to compile the project, it asks me for the password of the attached pfx file.

Unfortunately, I do not know the passwore anymore.

Even if I delete the pfx (to make a new pfx file) from the projet, it`s still asking me for the password of the pfx file. It seems like I cannot delete to pfx from the project. I am a little bit confused how to make the project run.

Is there a workaround? Any help?

Thanks!

  • Moved byYiChun ChenMSFTWednesday, October 07, 2009 7:05 AMDeployment issue (From:.NET Framework Setup)
  •  
ekomsdn  Monday, October 05, 2009 12:13 PM
Hi Ekomsdn,

I am moving this thread from Base ".NET Framework Setup" forum to the "ClickOnce and Setup & Deployment Projects" forum, since the issue is related to ClickOnce deployment. There are more deployment experts in the "ClickOnce and Setup & Deployment Projects" forum.

Thanks
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
YiChun Chen  Wednesday, October 07, 2009 7:04 AM

ekomsdn,

First, what version of the .NET Framework are you targeting, and are you doing manual or programmatic updates? There are a bunch of cases where your customers have to uninstall and reinstall the application if the certificate changes. Post back with some more info, and I'll tell you what the deal is with yours.

Second, go into the Signing tab and create a test certificate and make sure that's the one selected in the "Sign the ClickOnce manifests" box. Also uncheck "Sign the assembly" at the bottom of the page.

RobinDotNet


Click here to visit my ClickOnce blog!
Microsoft MVP, Client App Dev
RobinDotNet  Wednesday, October 07, 2009 7:30 AM
Hi ekomsdn,

Do you use the pfx file to sign your assembly as strong name assembly? Or do you have other pfx files which used to sign the assembly but have password?

Based on my test, when you select pfx file as strong name signing file, you won’t be asked for password. But when you select pfx file as ClickOnce manifest signing file, you will be asked for password if the file is protected by a password.

I suggest you can create a new pfx file with a password, let your ClickOnce application select that pfx file to sign the manifest. Since you know the password, you can move on to the next step.

If you have any question, please feel free to tell us.

Sincerely,
Kira Qian
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework!
Kira Qian  Wednesday, October 07, 2009 8:12 AM

You can use google to search for other answers

Custom Search

More Threads

• Advice on how to debug a installation problem.
• Expiration Date in Publish VS2005
• How to redistribute clickonce applications
• Installer throws exception
• Q: Prevent overwrite of db of existing app build in C#
• ClickOnce Update Problem
• Layout Bug with ClickOnce Installation/Update Dialog
• ClickOnce incorrectly tries to download from MS
• How can I embed .net runtime in exe application ?
• ClickOnce Error On Client Machine