I’m with Edhy. I never could get Click Once to work reliably, I switched to AppLife Update and deployments became a non-issue.
It’s very flexible, always works, and the support is terrific.

-Larry

Hi Ross,

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

Edhy Rijo

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

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"

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!

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

Bill,

Good sharing.

<<stands up>> I use the IDE too.

Glad you got it going. 

Keith

Keith Chisarik

"Hi. My name is Bill. I am a Visual Studio user."



When I closed the IDE this last time, a documentation update fired. I have no idea why there is suddenly a documentation update. I have not installed something new in quite a while. There have been many builds and exits since the last updates. This took quite a few minutes (as always). After that, I decided to fire up the IDE and publish locally. There were no issue. Then, I pushed the application out to the remote subnet...



There were no issues. It worked.







Go figure.



I guess the real problem might be the fact that in spite of these unusual, unsolveable problems, I am still using the IDE.



I am addicted.

I spent extra time clearing out ALL warnings in my build. There were about 26 that have been hanging around for a while...mostly just clean up related items. Even with them out of the picture, I still am having trouble. Now, though, it is worse. I published the app to my local subnet. It is stalling at the same point as the publication to the remote subnet. This time, though, there is no auto-generated web page, so I doubt it actually finished. The status is 'Ready' and the Output windows says:







That's it. The rest of the application properties window is disabled. I am stuck.



Canceling the publication and build. Time to remove temp files and such and try again.

Ok...after managing several necessary updates for our clients, I was able to get back to a point where I can publish the application, again. The local subnet went off without a hitch. The remote subnet is publishing now. It usually takes about 10 minutes.



(time passes)



The build is stuck. Same output:







Bummer. The interesting thing is that the remote location has all of the files that it needs to update the app. It works fine on their end. The publishing process just doesn't want to let go.



Well, I will look further and see what I can come up with. This seems to be another one of those annoying Visual Studio things.