我在async-await后面的曲线非常落后,所以这可能是一个“问题”。
我正在开发一个非常小的UI应用程序,该应用程序使用WPF NotifyIcon库从系统托盘运行。
应用程序应该以下列方式非常简单地运行(对用户而言):
我正在运行的问题是“异步执行开始”部分。在此之前发生的所有事情都可以正常工作,但是当程序开始尝试“运行”时,UI会锁定(我的意思是,用户可以像托盘图标上的疯狂人物一样点击并且上下文菜单拒绝显示)。
这种锁定发生的时间长得令人无法接受。
这是启动代码:
private async void AppStartup( object sender, StartupEventArgs e ) {
this.TRSIcon = this.FindResource( "TRSIcon" ) as TaskbarIcon;
if ( Settings.Default.DoUpgrade ) { //Upgrade if necessary.
Settings.Default.Upgrade( );
Settings.Default.DoUpgrade = false;
Settings.Default.Save( );
}
if ( string.IsNullOrEmpty( Settings.Default.Username ) || string.IsNullOrEmpty( Settings.Default.Password ) ) {
new Help( ).ShowDialog( );
Tuple<string, string> UP;
if ( ( UP = Login.Instance.GetUserPassword( ) ) != null ) {
Settings.Default.Username = UP.Item1;
Settings.Default.Password = UP.Item2;
Settings.Default.Save( );
} else
return;
}
await this.Start( ); //<-----This is where the meat of the program runs and it hangs the UI until it finishes.
return; //<-----This is just so that I have a break point to see that await this.Start is blocking (I have to do it like that right? or do I?)
}
这是Resources.xaml
:
<ResourceDictionary
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:Tools="clr-namespace:WPFTools.TaskbarNotification;assembly=WPFTools"
xmlns:TR="clr-namespace:TriviaRetriever">
<ContextMenu x:Key="TSRInterfaceMenu" x:Shared="false">
<MenuItem Header="Login" Command="{Binding cmdLogin}"/>
<MenuItem Header="Get My Trivia" Command="{Binding cmdDownload}"/>
<MenuItem Header="Register" Command="{Binding cmdRegister}"/>
<MenuItem Header="Lost Password" Command="{Binding cmdLostPassword}"/>
<MenuItem Header="About" Command="{Binding cmdAbout}"/>
<MenuItem Header="Log Out" Command="{Binding cmdLogout}"/>
<MenuItem Header="Exit" Command="{Binding cmdExit}"/>
</ContextMenu>
<Tools:TaskbarIcon
x:Key="TRSIcon"
MenuActivation="LeftOrDoubleClick"
IconSource="/TRIcon.ico"
DoubleClickCommand="{Binding cmdAbout}"
ContextMenu="{StaticResource TSRInterfaceMenu}">
<Tools:TaskbarIcon.DataContext>
<TR:TRSIViewModel/>
</Tools:TaskbarIcon.DataContext>
</Tools:TaskbarIcon>
</ResourceDictionary>
这是上下文菜单命令的MVVM:
public class TRSIViewModel {
public ICommand cmdLogin {
get {
return new DelegateCommand {
fncCanExecute = ( ) => ( Application.Current as App ).Core == null,
actCommand = async ( ) => {
Tuple<string, string> LoginPassword = Login.Instance.GetUserPassword( );
if ( LoginPassword != null ) {
Settings.Default.Username = LoginPassword.Item1;
Settings.Default.Password = LoginPassword.Item2;
Settings.Default.Save( );
await ( Application.Current as App ).Start( );
}
}
};
}
}
public ICommand cmdLogout {
get {
return new DelegateCommand {
fncCanExecute = ( ) => ( Application.Current as App ).Core != null,
actCommand = ( ) => {
( Application.Current as App ).Core.Terminate( );
( Application.Current as App ).Core = null;
}
};
}
}
public ICommand cmdRegister {
get {
return new DelegateCommand {
fncCanExecute = ( ) => true,
actCommand = ( ) => Process.Start( @"https://www.digigames.com/weekly_subscriptions/index.php" )
};
}
}
public ICommand cmdLostPassword {
get {
return new DelegateCommand {
fncCanExecute = ( ) => true,
actCommand = ( ) => Process.Start( @"https://www.digigames.com/weekly_subscriptions/lost_password.php" )
};
}
}
public ICommand cmdAbout {
get {
return new DelegateCommand {
fncCanExecute = ( ) => true,
actCommand = ( ) => ( Application.Current as App ).TRSIcon.ShowCustomBalloon( new About( ), PopupAnimation.Slide, 5000 )
};
}
}
public ICommand cmdExit {
get {
return new DelegateCommand {
fncCanExecute = ( ) => true,
actCommand = ( ) => {
if ( ( Application.Current as App ).Core != null )
( Application.Current as App ).Core.Terminate( );
Application.Current.Shutdown( 0 );
}
};
}
}
public ICommand cmdDownload {
get {
return new DelegateCommand {
fncCanExecute = ( ) => ( Application.Current as App ).Core != null,
actCommand = async ( ) => await ( Application.Current as App ).Core.DownloadTrivia( true )
};
}
}
public class DelegateCommand : ICommand {
public Action actCommand { get; set; }
public Func<bool> fncCanExecute { get; set; }
public bool CanExecute( object parameter ) {
return this.fncCanExecute != null && this.fncCanExecute( );
}
public event EventHandler CanExecuteChanged {
add { CommandManager.RequerySuggested += value; }
remove { CommandManager.RequerySuggested -= value; }
}
public void Execute( object parameter ) { this.actCommand( ); }
}
}
我在这里做错了什么?
答案 0 :(得分:2)
我认为您的问题与您的Start
方法有关。
但首先要做的事情。你的断点没有做你期望它做的事情。一旦Start
方法实际完成并且执行了剩余的函数,它就会中断,而不是一旦UI线程再次被释放。您必须了解,一旦执行在Start
函数中保留UI同步,UI线程就可以再次运行。
找出方法实际释放执行所需时间的好方法是等待它返回Task
对象。
var pendingTask = this.Start();
Debugger.Break();
await pendingTask;
Task
方法在内部异步执行的函数命中后返回Start
对象。 await
实际完成后pendingTask
会返回。
在你的情况下,我认为时间会相似,因为Start
方法没有向后台发送足够的工作。
有几种方法可以解决这个问题。如果您的Start
方法没有与UI交互,那么您没问题。您只需将整个方法发送到后台并完成它。这很简单:
await Task.Run(() => this.Start());
这会将任务发送到ThreadPool的一个线程中,并立即再次释放UI。 Task.Run
方法有一个重载,可以自动解包由Task
方法返回的内部Start
。
如果您的方法与UI交互,则必须在内部更改方法。查找方法内部需要很长时间但不与UI交互并将其包装到Task.Run
方法调用中的部分,如上所示。
每个await
将再次建立之前存在的SynchronizationContext
。因此,线程中能够改变UI的每个await
都将确保在同一个线程中执行延续。
这样的事情没有问题:
someLabel.Label = "Working…";
await Task.Run(() => DoManyThings());
someLabel.Label = "Done! :D"
我希望有所帮助。在不知道Start
方法的作用的情况下,我无法给你更多提示。但我希望这个答案能让你走上正轨。
我通常的免责声明:我通常使用VB.net,所以我的C#代码在语法方面可能存在缺陷。如果您发现任何错误,请随时编辑或告诉我有什么问题。
答案 1 :(得分:1)
只需创建一个新的Thread
并将其运行即可。
private void App_OnStartup(object sender, StartupEventArgs e)
{
//Some login logic
if(loggedIn) //Or however you do it
{
Thread thread = new Thread(() =>
{
this.RunWhateverMethodWillDoABunchOfStuff()
});
thread.SetApartmentState(ApartmentState.STA);
thread.Start();
}
根据确切的程序和你想要的,你也可以使用BackgroundWorker
,这是一个很好的ansync方式来运行背景操作,同时从backgrund线程接收进度更新,允许你更新类似的东西加载栏或类似的东西。如果您想了解更多信息,请告诉我
编辑2:以下是任何关心
的人BackgroundWorker
方法的示例
BackgroundWorker bw = new BackgroundWorker();
bw.DoWork += BwOnDoWork;
bw.ProgressChanged += BwOnProgressChanged;
bw.RunWorkerCompleted += BwOnRunWorkerCompleted;
bw.WorkerSupportsCancellation = true;
bw.WorkerReportsProgress = true;
//This line here is what starts the asynchronous work
bw.RunWorkerAsync();
private void BwOnRunWorkerCompleted(object sender, RunWorkerCompletedEventArgs runWorkerCompletedEventArgs)
{
//Do whatever you want to do when it is done with its asynchronous task
//for example
Label.Content = "Yay, Were done doing whatever it was that we were doing!!!!"
}
private void BwOnProgressChanged(object sender, ProgressChangedEventArgs e)
{
//Here is where we can send progress reports to the UI, like updating a loading bar
MyProgressBar.EditValue = e.ProgressPercentage;
}
private void BwOnDoWork(object sender, DoWorkEventArgs doWorkEventArgs)
{
//This is where we will put anything we want to be ran asynchronously
this.RunWhateverMethodWillDoABunchOfStuff()
}