I publish my updates to a network location. Actually, there are two locations. The first location, which is on my local subnet, has no problems. The second, remote location does get the app published and everyone can install it and use it; however, my Visual Studio remains in a "Publishing..." state. The browser page stating the publication has been successful does show up. All of the necessary files are on the network share. VS2008 just doesn't want to finish the job. Has anyone run into this? Any VS2008 clean-up tricks I should employ?



Thanks!

Bill

It is happening again. The remote subnet gets the update but the IDE does not stop the publishing process. Just fyi.

Let me just say this one thing....I am glad we moved away from Click-Once Deployment!



I have nothing to offer since I was never a fan of this logic and it was not sophisticated enough for our medical application. I know that once you get it working it can be nice...but the larger an application becomes, the more of this I always see until eventually a move is made.



Good luck, I hope that you come up with a solution soon!

Bill,



I never use remote publishing. I.e. I publish local and then copy files myself (though that could be automated). You just have to differentiate between were the files will be copied and the URL that is used for installation and/or updates.



Oh..."I'm an IDE user too"

What do you use to allow users to update their desktop app rather than "click once"?

Hi Ross,

I use AppLifeUpdate from kineticjump, excellent tool, great support and better yet, it does work all the time.

Edhy Rijo