The simplest way to solve the problem where C # performs time-consuming methods in the UI thread causes the interface to suspend animation

int sta =  my_connect.login (_user_name, _password);

As above, the login method through HTTP to the server to send a request, in the network condition is not good or the server is busy, because the delay can not return results caused the page suspended animation.

Solution:

int sta = await task.run (() =>
            {return
                my_connect.login (_user_name, _password);
            });

Awit keyword waits for task to complete

Task.run opened up a new thread

In this way, the UI thread is not blocked and solves the problem of suspended animation of the interface.

There are many ways to multithreading, but because. NET does not allow access to controls on non-UI threads, the above approach is most appropriate for situations where the UI needs to be updated after the long time-consuming task has finished executing.