ci: generate artifacts #62
DexrnZacAttackAnnotations
20 warnings
|
build (Debug):
Utils/Packages.cs#L215
Converting null literal or possible null value to non-nullable type.
|
|
build (Debug):
Pages/Settings/UiSettingsPage.xaml.cs#L77
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.
|
|
build (Debug):
Pages/Settings/UiSettingsPage.xaml.cs#L56
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.
|
|
build (Debug):
Dialogs/ProgressController.cs#L58
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.
|
|
build (Debug):
Dialogs/ProgressController.cs#L62
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.
|
|
build (Debug):
Dialogs/ProgressController.cs#L43
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.
|
|
build (Debug):
Dialogs/ProgressController.cs#L47
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.
|
|
build (Debug):
Settings/InstalledPackages.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (Debug):
Settings/InstalledPackages.cs#L76
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (Debug)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
build (Release):
Pages/AppsListPage.xaml.cs#L460
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.
|
|
build (Release):
Pages/Settings/UiSettingsPage.xaml.cs#L77
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.
|
|
build (Release):
Pages/Settings/UiSettingsPage.xaml.cs#L56
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.
|
|
build (Release):
Dialogs/ProgressController.cs#L58
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.
|
|
build (Release):
Dialogs/ProgressController.cs#L62
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.
|
|
build (Release):
Dialogs/ProgressController.cs#L43
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.
|
|
build (Release):
Dialogs/ProgressController.cs#L47
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.
|
|
build (Release):
Settings/InstalledPackages.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (Release):
Settings/InstalledPackages.cs#L76
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (Release)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
WinDurangoUI-Debug
|
30.9 MB |
sha256:1c3fbf6a84a7787584ba49bc3252c165db13db4b9faaf77cb8a4663133e17eb1
|
|
|
WinDurangoUI-Release
|
30.9 MB |
sha256:33d264f36526ade595a0142d697cf864684b04ccc4418efec0858998314b7d56
|
|