Preferred "updating" paradigm with WinForms
-
I'm working on a WinForms app which talks to a webservice. With an Ajax app you'd use an "updating" gif, which would disappear once everything had completed - I was wondering if anyone knows of a preferred/standard approach when dealing with WinForms?
"It was the day before today.... I remember it like it was yesterday." -Moleman
-
I'm working on a WinForms app which talks to a webservice. With an Ajax app you'd use an "updating" gif, which would disappear once everything had completed - I was wondering if anyone knows of a preferred/standard approach when dealing with WinForms?
"It was the day before today.... I remember it like it was yesterday." -Moleman
If the updating via the web service is going to take a long time ie keep the user waiting, then ideally you should do the update on a different thread from that of the UI. In VS 2005 you can use the BackgroundWorker control for this purpose. A quick and dirty solution would be to lock down the UI and use a PictureBox control to display the 'updating' gif as in Ajax or alternatively use a ProgressBar.