Some dev tests #29
Annotations
20 warnings
Publish 32-bit WPF application:
SA-Mod-Manager/Configuration/SADX/GameSettings.cs#L823
'GameSettings.Patches' is obsolete
|
Publish 32-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L279
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.
|
Publish 32-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L475
'GameSettings.Patches' is obsolete
|
Publish 32-bit WPF application:
SA-Mod-Manager/Controls/SA2/GameConfig.xaml.cs#L206
'GameSettings.Patches' is obsolete
|
Publish 32-bit WPF application:
SA-Mod-Manager/ModInfo.cs#L141
The event 'ModData.PropertyChanged' is never used
|
Publish 32-bit WPF application:
SA-Mod-Manager/ModInfo.cs#L150
The event 'CodeData.PropertyChanged' is never used
|
Publish 32-bit WPF application:
SA-Mod-Manager/UI/Models/MainWindowViewModel.cs#L19
The event 'MainWindowViewModel.PropertyChanged' is never used
|
Publish 32-bit WPF application:
SA-Mod-Manager/Util.cs#L751
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
Publish 32-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L279
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.
|
Publish 32-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L475
'GameSettings.Patches' is obsolete
|
Publish 64-bit WPF application:
SA-Mod-Manager/Controls/SA2/GameConfig.xaml.cs#L206
'GameSettings.Patches' is obsolete
|
Publish 64-bit WPF application:
SA-Mod-Manager/Configuration/SADX/GameSettings.cs#L823
'GameSettings.Patches' is obsolete
|
Publish 64-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L279
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.
|
Publish 64-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L475
'GameSettings.Patches' is obsolete
|
Publish 64-bit WPF application:
SA-Mod-Manager/ModInfo.cs#L150
The event 'CodeData.PropertyChanged' is never used
|
Publish 64-bit WPF application:
SA-Mod-Manager/ModInfo.cs#L141
The event 'ModData.PropertyChanged' is never used
|
Publish 64-bit WPF application:
SA-Mod-Manager/UI/Models/MainWindowViewModel.cs#L19
The event 'MainWindowViewModel.PropertyChanged' is never used
|
Publish 64-bit WPF application:
SA-Mod-Manager/Util.cs#L751
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
Publish 64-bit WPF application:
SA-Mod-Manager/Configuration/SADX/GameSettings.cs#L823
'GameSettings.Patches' is obsolete
|
Publish 64-bit WPF application:
SA-Mod-Manager/Controls/SADX/GameConfig.xaml.cs#L279
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.
|
Loading