The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

The field 'TaskBase._insideIsIndeterminate' is never used

The field 'SettingBackgroundService._telemetryClient' is never used

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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 'SettingBackgroundService._telemetryClient' is never used

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

The field 'TaskBase._insideIsIndeterminate' is never used

Avoid awaiting or returning a Task representing work that was not started within your context as that can lead to deadlocks.

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, Blessing-Studio/get-csproj-version@main, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

The field 'TaskBase._insideIsIndeterminate' is never used

The field 'SettingBackgroundService._telemetryClient' is never used

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

Avoid awaiting or returning a Task representing work that was not started within your context as that can lead to deadlocks.

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, Blessing-Studio/get-csproj-version@main, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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 'TaskBase._insideIsIndeterminate' is never used

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

The field 'SettingBackgroundService._telemetryClient' is never used

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, Blessing-Studio/get-csproj-version@main, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

The field 'TaskBase._insideIsIndeterminate' is never used

The field 'SettingBackgroundService._telemetryClient' is never used

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

Avoid awaiting or returning a Task representing work that was not started within your context as that can lead to deadlocks.

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.

Field 'TaskBase._insideProgressDetail' is never assigned to, and will always have its default value null

The field 'TaskBase._insideIsIndeterminate' is never used

Field 'TaskBase._insideProgress' is never assigned to, and will always have its default value 0

The field 'SettingBackgroundService._telemetryClient' is never used

Avoid awaiting or returning a Task representing work that was not started within your context as that can lead to deadlocks.

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

Avoid method overloads that assume TaskScheduler.Current. Use an overload that accepts a TaskScheduler and specify TaskScheduler.Default (or any other) explicitly. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD105.md)

The following actions uses node12 which is deprecated and will be forced to run on node16: nelonoel/branch-name@v1, marvinpinto/action-automatic-releases@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: nelonoel/branch-name@v1, actions/download-artifact@v3, marvinpinto/action-automatic-releases@latest. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/