W
Wolfbane
Guest
I have a well established quick once application which uses both C++ and C# code. The application is deployed using Click Once. Click Once has proved to be a reliable and efficient method of distributing the application worldwide. However, recently our customers have been reporting the application freezing before if reaches the main welcome screen. After some investigation I have discovered the reason for this is that the application cannot find the distribution server. As a separate issue the reason for that was because the distribution server has been under constant attack by hackers.
However, it appears that if Click Once cannot contact the distribution server it just sits and waits...and waits... and waits, you get the picture. Only recourse is to stop the application. Is there any way to modify Click Once so that if it cannot find the distribution server it times out produces a message, forgets about checking for an update and then moves on to the main application?
Continue reading...
However, it appears that if Click Once cannot contact the distribution server it just sits and waits...and waits... and waits, you get the picture. Only recourse is to stop the application. Is there any way to modify Click Once so that if it cannot find the distribution server it times out produces a message, forgets about checking for an update and then moves on to the main application?
Continue reading...