Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Found markup element with unexpected name 'TableCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableRowComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableHeaderCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableHeaderCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableHeaderCellComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableRowComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'TableComponent'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'Nav'. If this is intended to be a component, add a @using directive for its namespace.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

'DataBinder' is obsolete: '🚨 Do not use the DataBinder long-term in your projects. See LINK for documentation about how to migrate from the DataBinder 🚨'

Found markup element with unexpected name 'ChildNodes'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'ChildNodes'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'ChildNodes'. If this is intended to be a component, add a @using directive for its namespace.

Found markup element with unexpected name 'ChildNodes'. If this is intended to be a component, add a @using directive for its namespace.

Obsolete member 'Button.PostBackUrl' overrides non-obsolete member 'ButtonBaseComponent.PostBackUrl'

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period