You cannot start application from this location because it is already installed

You cannot begin application from this place because it is already installed from a various location

I got it by doing the following: * I develop my deployment and zip it. * Go to an install computer and unzip and also install. * Create the next variation and also zip that up. * Now on my install computer system, if I unzip to a various location and also attempt to run setup, I obtain the above error.

I would be perfectly fine through having my application totally uninstall previous versions and then install the latest. Would not these forms of errors happen all the time wbelow a user installs from a DVD once and later gets a new variation via a downloaded ZIP file?

You watching: You cannot start application from this location because it is already installed



See more: X-Auth-Error Orgidmailboxnotfoundexception, Trouble Logging Into Hotmail

The deployment URL is part of the identification of the application. If you install it from one place when it starts, you must install updates from the exact same area. It does this also if you do not specify a deployment provider in the manifest (as listed in the write-up referenced by Johnny) -- it just sets it to the location you initially install it from.

The just means approximately this that I understand of is to publish the application to a webserver as an online-only application. (Might also job-related from a document share, but I don"t remember.)

See more: How To Install Windows 10 On Nuc, Byopc: Getting Up And Running With Intel Nuc


If you desire to install various versions of the very same application making use of ClickOnce at the very same time, such as a Dev version and also a QA version, then authorize each variation through unique certificates:

Get-PfxCertificate -FilePath .MyApp-Q1.pfxThen have the adhering to in your app csproj file:

MyApp - Q1\myinstallationlink9D4BF3492523A7D45A835542F7E1CB27ED53573B../Certificates/MyApp-Q1.pfxOr alternatively if you like a UI-based solution, you deserve to go to the job properties in Visual Studio and also click the Signing tab to add a certificate tright here. For details, please view MSDN How to: Sign application and also deployment manifests (see or Walkthrough: Manually deploy a ClickOnce application (view