Unexpected input(s) 'clickonce-application-name', 'clickonce-publisher-name', valid inputs are ['azure-tenant-id', 'azure-client-id', 'azure-client-secret', 'azure-client-certificate-path', 'azure-client-send-certificate-chain', 'azure-username', 'azure-password', 'endpoint', 'code-signing-account-name', 'trusted-signing-account-name', 'certificate-profile-name', 'files', 'files-folder', 'files-folder-filter', 'files-folder-recurse', 'files-folder-depth', 'files-catalog', 'file-digest', 'timestamp-rfc3161', 'timestamp-digest', 'append-signature', 'description', 'description-url', 'generate-digest-path', 'generate-digest-xml', 'ingest-digest-path', 'sign-digest', 'generate-page-hashes', 'suppress-page-hashes', 'generate-pkcs7', 'pkcs7-options', 'pkcs7-oid', 'enhanced-key-usage', 'exclude-environment-credential', 'exclude-workload-identity-credential', 'exclude-managed-identity-credential', 'exclude-shared-token-cache-credential', 'exclude-visual-studio-credential', 'exclude-visual-studio-code-credential', 'exclude-azure-cli-credential', 'exclude-azure-powershell-credential', 'exclude-azure-developer-cli-credential', 'exclude-interactive-browser-credential', 'timeout', 'batch-size', 'cache-dependencies', 'trace']

Unexpected input(s) 'clickonce-application-name', 'clickonce-publisher-name', valid inputs are ['azure-tenant-id', 'azure-client-id', 'azure-client-secret', 'azure-client-certificate-path', 'azure-client-send-certificate-chain', 'azure-username', 'azure-password', 'endpoint', 'code-signing-account-name', 'trusted-signing-account-name', 'certificate-profile-name', 'files', 'files-folder', 'files-folder-filter', 'files-folder-recurse', 'files-folder-depth', 'files-catalog', 'file-digest', 'timestamp-rfc3161', 'timestamp-digest', 'append-signature', 'description', 'description-url', 'generate-digest-path', 'generate-digest-xml', 'ingest-digest-path', 'sign-digest', 'generate-page-hashes', 'suppress-page-hashes', 'generate-pkcs7', 'pkcs7-options', 'pkcs7-oid', 'enhanced-key-usage', 'exclude-environment-credential', 'exclude-workload-identity-credential', 'exclude-managed-identity-credential', 'exclude-shared-token-cache-credential', 'exclude-visual-studio-credential', 'exclude-visual-studio-code-credential', 'exclude-azure-cli-credential', 'exclude-azure-powershell-credential', 'exclude-azure-developer-cli-credential', 'exclude-interactive-browser-credential', 'timeout', 'batch-size', 'cache-dependencies', 'trace']

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.

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 event 'LcmThreadedProgress.Canceling' is never used

Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)

Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)

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.

Parameter 'dbContext' is unread.

The variable 'e' is declared but never used

Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)

Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)

Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)

GetResult synchronously blocks. Use await instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD103.md)

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.

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 event 'LcmThreadedProgress.Canceling' is never used

Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)

Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)

Parameter 'dbContext' is unread.

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.