[RESOLVED] ClickOnce Installer

I have a ClickOnce app that has been working fine for a couple months, until a day or two back some internal politics borked the server. The result of this was that the path for ClickOnce during install changed just slightly at one intermediate level. It used to have /is/ in the path, and the is has changed to something else. I changed everything I could find, including recreating the whole target directory in IIS on the server. However, when I publish, though the link is correct, installation is failing. The log shows that, after checking and installing some prerequisites, the installation is attempting to go back to that /is/ path to find the app for installation.

Can anybody suggest where that invalid path is located? I have gone through every property I can find in Project|Properties, and they are correct. I have looked in App.config, and that is correct. Where else should I be looking?

I'm a little fuzzy on the details, but I think it's part of the Manifest file that signed during the publish process... at least that's the case here. When ever we move to one of the many environments we have here, the app has to be re-published with a new manifest to allow it to work on the new server.

-tg

What do you have to do to force a new manifest?

And that's where I'm a little fuzzy on the details... we've got a special app that is a bit of a black box to me that does it... All I know is that the manifest file is only good for one location. Wish I could be of more help.

-tg

Your suggestion certainly gave me a point to start looking. Unfortunately, I looked in detail, and my manifest is pointing to the right URL. That doesn't appear to be the solution in this case. In fact, it looks like I have already crossed that bridge. I do have one idea that is so dumb I'm not going to mention it until I have tried it...quietly...in a secluded place...alone. My one positive note about the idea is the Holmes principle: Once you have tried everything reasonable, whatever is left, no matter how unreasonable, has to be the answer. Results on Tuesday.

If anybody has any other suggestions, I am still open to ideas.

The solution proved to be kind of odd. I removed all the prerequisites, published, put back all the prerequisites, and published again. That solved it. One of the prerequisites was holding a reference to the old server, though I'm still not sure where.

huh.... well, glad you got it solved.

-tg

I suspect one prerequisite in particular, but only because I don't suspect the others, which is mighty slim evidence.