When ever I try and publish my project in VS 2005 I get an error
default certificate could not be created publish aborting. Any idea what is going on?
It is a VB project and it runs fine no errors. I am choosing to deploy to a local directory
C:\deploy\firstproject. I have tried online help and nothing comes up on this error.
Any help would be appreciated.
-Troy
hi,
i also got the same problem. (but i'm using Visual C# Express Edtions)
How to sign the project? i've tried project properties then signing then check sign the clickOnec manifests but still got the same error.
anyone please tell me how to solve this problem?
thanks in advance
CAN ANYONE HELP?
I'm getting the same error, too. I've created a small windows form application that I want to publish as an executable. It's a simple check-digit creator that other people at my office are using a spreadsheet to do; I thought a little app would be easier for them to use.
I've created the app, tested and debugged it, and now it's ready to go. I am getting the same error when I go to publish the app. Looking up the creation of certificates and publishing of applications in the help, I'm told that I need to go to the project property pages dialog box and tick 'authenticode signature' if I'd like to enable signing, and enter pathnames to valid certificate and private key files. Trouble is, there IS no 'authenticode signature' box to tick, however there is a 'signing' tab. Even though none of the boxes are ticked in this tab, the application publisher still wants to create some sort of default certificate. The information on creating / obtaining certificates assumes much prior knowledge of signatures, keys, certificate containers, and the like - it might be me, but I cannot determine what I need to do to get my application properly built.
Microsoft, you're making it hard to want to use your development tools. I was going to reproduce my small app in C# perhaps, but it looks as if the problem is there as well. I'll check back to see if anyone can help, in the meantime I'll go use Mono and see how that goes.
Troy, I feel for ya. :) I had even thought the problem was because I moved my app over to a different machine and different installation of VS express during its development, and so I BUILT IT AGAIN in this environment just to see. Thank goodness it was tiny. Meanwhile Bill sits in his office and reads emails for several hundred dollars a minute. Thanks, Bill. Another quality product. Beautiful development environment but not much use when you can't build your end product.
check out this link guys
Hello,
I'm stuck with the same problem.
I hope Microsoft will giva a solution because the meaning of building programs is to USE them !!!
