Process completed with exit code 1.

The job was canceled because "netcoreapp3_1" failed.

The operation was canceled.

The job was canceled because "netcoreapp3_1" failed.

The operation was canceled.

The job was canceled because "netcoreapp3_1" failed.

The operation was canceled.

The job was canceled because "netcoreapp3_1" failed.

The operation was canceled.

Assets file 'D:\a\ExpressionEngine\ExpressionEngine\ExpressionEngine\obj\project.assets.json' doesn't have a target for 'net7.0'. Ensure that restore has run and that you have included 'net7.0' in the TargetFrameworks for your project.

Assets file 'D:\a\ExpressionEngine\ExpressionEngine\ExpressionEngine\obj\project.assets.json' doesn't have a target for 'net7.0'. Ensure that restore has run and that you have included 'net7.0' in the TargetFrameworks for your project.

Process completed with exit code 1.

The job was canceled because "net7_0" failed.

The job was canceled because "net7_0" failed.

The operation was canceled.

The job was canceled because "net7_0" failed.

Assets file 'D:\a\ExpressionEngine\ExpressionEngine\ExpressionEngine\obj\project.assets.json' doesn't have a target for 'netcoreapp3.1'. Ensure that restore has run and that you have included 'netcoreapp3.1' in the TargetFrameworks for your project.

Assets file 'D:\a\ExpressionEngine\ExpressionEngine\ExpressionEngine\obj\project.assets.json' doesn't have a target for 'netcoreapp3.1'. Ensure that restore has run and that you have included 'netcoreapp3.1' in the TargetFrameworks for your project.

The operation was canceled.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. 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 use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-dotnet@v3, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.

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

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.

Missing XML comment for publicly visible type or member 'IExpressionEngine'

Missing XML comment for publicly visible type or member 'IExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'IExpressionEngine.ParseToValueContainer(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ExpressionEngine(ExpressionGrammar)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ParseToValueContainer(string)'

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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 use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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 node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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 use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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 "--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.

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

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.

Missing XML comment for publicly visible type or member 'IExpressionEngine'

Missing XML comment for publicly visible type or member 'IExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'IExpressionEngine.ParseToValueContainer(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ExpressionEngine(ExpressionGrammar)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ParseToValueContainer(string)'

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.

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

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.

Missing XML comment for publicly visible type or member 'IExpressionEngine'

Missing XML comment for publicly visible type or member 'IExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'IExpressionEngine.ParseToValueContainer(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ExpressionEngine(ExpressionGrammar)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.Parse(string)'

Missing XML comment for publicly visible type or member 'ExpressionEngine.ParseToValueContainer(string)'

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.

ProjectReference 'D:\a\ExpressionEngine\ExpressionEngine\ExpressionEngine\ExpressionEngine.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v3.1'. This project may not be fully compatible with your project.

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.