I am using vb.net vs2005 sql server2005

When i publish to a file location, i get this.

I have been publishing to a file folder all year without a problem. Apparently there is a certificate that had expired on July 2, 2009.
I dont want to use certificates at all. I just want to be able to re-publish when i make a change, and have my users get that change.

All i want to do is publish to a file folder, and have the users "one click" run the app.
When iuncheck the "Sign theClickOnce manifest" , the process of publishing it re-checks it.
I also uncheck the"Enable ClickOnce Security setting". But the publish funtion also forces a check mark there as well.

It there any way to disable the certificate part of this, so that i can simply publish to a file location and have my users be able to run the app without it expiring in a year or without any certificate involvement at all???????

Thank You
Jerry Cicierega

You can use makecert to create a test certificate with a date really far in the future (http://msdn.microsoft.com/en-us/library/bfsktky3(VS.80).aspx).

With VS2008 SP1, you won't have to sign your deployments (http://msdn.microsoft.com/en-us/library/che5h906.aspx), so if signing is a major issue, you can upgrade. But if you don't need any of the additional nifty ClickOnce features of 3.5 SP1, I would stick with what you've got and just create a certificate that doesn't expire for a while.

HTH,
Jennifer

You can use makecert to create a test certificate with a date really far in the future (http://msdn.microsoft.com/en-us/library/bfsktky3(VS.80).aspx).

With VS2008 SP1, you won't have to sign your deployments (http://msdn.microsoft.com/en-us/library/che5h906.aspx), so if signing is a major issue, you can upgrade. But if you don't need any of the additional nifty ClickOnce features of 3.5 SP1, I would stick with what you've got and just create a certificate that doesn't expire for a while.

HTH,
Jennifer