You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have recently found that developer should use WorkAsync very accurately, since sometimes user may get really unpredictable results:
When code inside this statement calls something like MessageBox.Show, for example to inform user about something went wrong, the yellow window will keep staying on top of application screen and will be impossible to close it at all;
WorkAsync really helps when something should be done asynchronously, but when I tried to establish several asynchronous processes in the same time it become really painful to make it work together.
I think we might rewrite this functionality in the way to use new Tasks feature in .NET 4.5. Interface of the method might remain the same for simple operations done by developer, however it should be an option to start advanced processing like start several simultaneous tasks and wait for them all to finish.
And more control on what is shown in the information pane.
The text was updated successfully, but these errors were encountered:
shytikov
changed the title
WorkAsync method issue
WorkAsync method issue
Feb 24, 2015
I have recently found that developer should use
WorkAsync
very accurately, since sometimes user may get really unpredictable results:WorkAsync
really helps when something should be done asynchronously, but when I tried to establish several asynchronous processes in the same time it become really painful to make it work together.I think we might rewrite this functionality in the way to use new
Tasks
feature in .NET 4.5. Interface of the method might remain the same for simple operations done by developer, however it should be an option to start advanced processing like start several simultaneous tasks and wait for them all to finish.And more control on what is shown in the information pane.
The text was updated successfully, but these errors were encountered: