cross compile dotnet app #34
Annotations
8 errors and 8 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.
|
|
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.
|
The logs for this run have expired and are no longer available.
Loading