Improve support for nested postman collection items #77
Annotations
8 errors and 9 warnings
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
build dotnet executables
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
|
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
|
build dotnet executables
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.
|
Loading