Support for Asp.Net Core running on UWP as Windows IoT Core Background Task
Currently there is no support for Kestrel on UWP as Windows IoT Core Background Task. As Microsoft is trying to push Windows IoT Core, getting Asp.Net Core to run on that platform would be ideal. It is a real showstopper that there isn't any support for it.
Guys this needs to be implemented, in every flavour of UWP we are hitting this due to referencing Universal Windows Class Libraries that reference NetStandard 2.0 nuget packages that contain calls to AspNetCore components. When compiling in .NetNative the warning window lights up with ILTransform and P/Invoke warnings all pointing at ASPNetCore calls missing in the UWP Windows implementation
Why is the voting closed?
Running a web server as a UI and/or an API is a very common scenario with IoT systems. Having asp.net core support for this would be a huge benefit.
Rick Purtee commented
A use case for ASP.NET Core has a background process:
The Iot computer is used to drive a sign board display that is updated from either REST API, or a locally hosted website.
Gerard “garfius” Forcada commented
Pleeease, otherwise it's just a brick and needs a screen.
Agreed. Plus we can update those apps through the same Azure IoT Hub DM mechanism which is most common for UWP apps running on IoT Core. It would seem that attempting to do this with the .NET Core EXE deployment would be more complicated.
Hosting simple web server in same process with background task makes many things way easier for developers:
1. We can use familiar ASP.NET Core and related tooling
2. We don't have to invent mechanisms for inter-process communication
3. We have to write way less risky code
kevin supinger commented
This is very necessary to support WebApi in background tasks just like in Windows Services using self hosted ASP.NET server