[Shane Brodie]

Greetings:

I have an extremely frustrating issue. I have an application created within
VS 2005 using VB.Net and deployed to a network share using ClickOnce
deployment. I was asked to also create a traditional setup for deploying
the application. I added a traditional Windows Forms Setup project and all
worked well for both deployment methods.

My supervisor then decided to only use ClickOnce deployment. I decided to
remove the setup project from my solution. From this point on, ClickOnce
has failed to work for deploying my application.

The problem is that the ClickOnce deployment fails to update the manifests
with the correct deployment manifest version number. Regardless what is
displayed on the Publish tab within VB 2005, the IDE (or a tool launched by
the IDE in the background) sets the version of the manifest to 1.0.0.50.
This happens even though my Publish version is set to 1.5.0.0 (or any other
valid value for that matter).

I have tried:

I have tried uninstalling my local copy of the app.
Deleted any relevant registry entries I could locate.
Removing all compiled binaries and manifests and regenerating them.
Scanned project all files for "1.0.0.50" - none found
Deleted all Visual Studio related files in my profile.
Search the web for ideas - nada relevant.

All to no avail. I still cannot deploy this one application. My supervisor
can grab the latest source from our repository and compile and deploy
without issues.

Any ideas?

Archived from group: microsoft>public>vb>deployment

["Jan Hyde]

"Shane Brodie" 's wild thoughts were
released on Thu, 29 Nov 2007 12:10:13 -0600 bearing the
following fruit:

>Greetings:
>
>I have an extremely frustrating issue. I have an application created within
>VS 2005 using VB.Net and deployed to a network share using ClickOnce
>deployment.

This is a VB6 group, you need a group with 'dotnet' in the
name.
--
Jan Hyde

https://mvp.support.microsoft.com/profile/Jan.Hyde