We have a prototype application that was originally published to an external server hosted on AWS (for discussions sake assume this was on http://prototypes.mysever.com/MyApp/).
The prototype size started to mount up so for speed we moved it to an internal server (assume http://internal/MyApp/).
I did some clearing out of our IIS server that was hosting the original published app (external) and removed the application. Now if we try to install a copy of the app, it fails, because it wants to talk to the original server even though we published it elsewhere (for like 80+ versions).
In the .application file I noticed a reference to the old server, but changing this didn’t solve our problems.
Is there a way to stop it looking for the old server?
Sorry,
I deleted my last answer, because I misunderstood the question. Yes, there is a way to change the update location.
Open the Project properties page, and go to the Publish tab.
Click the Updates… button.
On the updates screen, verify that the update location is pointing to the new location.