Open peterhuene opened 5 years ago
See also dotnet/sdk#2700 which worked around the lack of the API for Nano Server.
Cc @dsplaisted @nguerrera @jkotas @sbomer for awareness regarding this tracking issue.
@jkotas is doing a cross-platform resource updater for the apphost customization still on the radar for 3.0?
I do not know. Is it acceptable to ship without it? @jeffschwMSFT @vitek-karas
Currently this request is below our feature line for .NET Core 3.0. We were aware of this request when we started this work, but decided to hold for strong customer need before investing.
Looks like the path forward here is: https://github.com/dotnet/core-setup/pull/6831#issuecomment-502876821
cc @jkoritzinsky @swaroop-sridhar @davidwrighton
Any progress on a solution to this? Or a suitable workaround? I use linux for my build server and would love to be able to build Windows Desktop binaries. Not even Avalonia, Uno Platform or JBildstein/SpiderEye can build windows binaries at this time, forcing me on .net 4.8, unless I want no icon and a console window.
Steps to reproduce
On Windows with Docker for Windows installed that has been configured to use "Windows Containers":
docker run -it microsoft/dotnet-nightly:3.0-sdk
mkdir repro && cd repro
dotnet new console
dotnet build
Expected behavior
The project builds without warnings or errors. The resulting apphost is customized.
Actual behavior
A warning is printed that the application host will not be customized because the Docker
This is because the resource updating API (starting with
BeginUpdateResource
) isn't available on Nano Server.Given that CI systems might be using Nano Server to build applications, users will likely want this to work so that their build doesn't differ from other platforms.
Environment data