I\'m using Visual Studio 2008 SP1.
I have a Windows Forms application deployed internally using ClickOnce in a shared folder on the local network.
The test c
Did you change your target CPU from Any CPU to x86?
If you changed this, you will have to reinstall the application.
What do you mean when you say the following? "Changes: I set Suite Name value; Version and #AdministradorWin.app, vs #AdministradorWin.application".
It's the last bit I'm interested in. Did you change the assembly name?
There are a handful of settings that make up the identity of the deployment. Target CPU (as noted by zezespecial above), installation URL, and assembly name are three of them. Did you change any of these? What other changes did you make to the deployment?
In my case, using Azure DevOps Pipelines, the project setting that generates the manifests got accidentally set to false somehow. I noticed it while comparing source control history versions of the project file. My fix was to manually (re)insert this property group into the csproj project file:
<PropertyGroup>
<GenerateManifests>true</GenerateManifests>
</PropertyGroup>
'Check Publish -> Installation Folder URL' and make sure it is not set incorrectly (sometimes it only shows up during publishing process)
'Check Publish -> Updates...' and make sure the Update Location is not set incorrectly.
To be absolutely sure set both these to be the same as the Publishing Folder Location. You'll need to tick 'The Application should check for update - Before the application starts'.
I had to do this to fix issue in my case.