1.1.4 #196
Annotations
20 warnings
Release:
SA-Mod-Manager/Common/GamesInstall.cs#L666
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/ModsCommon/OneClickInstall.xaml.cs#L44
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L359
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L1542
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L1585
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/UI/MainWindowViewModel.cs#L17
The event 'MainWindowViewModel.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/ModInfo.cs#L142
The event 'ModData.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/ModInfo.cs#L151
The event 'CodeData.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/GitHub.cs#L290
The field 'GitHub.AppName' is assigned but its value is never used
|
Release:
SA-Mod-Manager/Common/GamesInstall.cs#L666
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/Common/GamesInstall.cs#L666
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/ModsCommon/OneClickInstall.xaml.cs#L44
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L359
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L1542
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/UI/MainWindow.xaml.cs#L1585
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Release:
SA-Mod-Manager/UI/MainWindowViewModel.cs#L17
The event 'MainWindowViewModel.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/ModInfo.cs#L151
The event 'CodeData.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/ModInfo.cs#L142
The event 'ModData.PropertyChanged' is never used
|
Release:
SA-Mod-Manager/GitHub.cs#L290
The field 'GitHub.AppName' is assigned but its value is never used
|
Release:
SA-Mod-Manager/ModsCommon/OneClickInstall.xaml.cs#L44
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|