Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-dotnet@v1, microsoft/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

.NET 5.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.

The field 'MainWindow.disposedValue' is never used

The field 'MainWindow.disposedValue' is never used

The field 'MainWindow._timerFlag' is assigned but its value is never used

The field 'MainWindow._timerFlag' is assigned but its value is never used

Non-nullable field '_core' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

Nullability of reference types in type of parameter 'sender' of 'void MainWindow.Core_OnError(object sender, ErrorsEventArgs e)' doesn't match the target delegate 'EventHandler<ErrorsEventArgs>' (possibly because of nullability attributes).

Nullability of reference types in type of parameter 'sender' of 'void MainWindow.Core_OnError(object sender, ErrorsEventArgs e)' doesn't match the target delegate 'EventHandler<ErrorsEventArgs>' (possibly because of nullability attributes).

Cannot convert null literal to non-nullable reference type.

Non-nullable field '_core' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

Nullability of reference types in type of parameter 'sender' of 'void MainWindow.Core_OnError(object sender, ErrorsEventArgs e)' doesn't match the target delegate 'EventHandler<ErrorsEventArgs>' (possibly because of nullability attributes).

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.

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.

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.

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.

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.

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.

The field 'MainWindow.disposedValue' is never used