Most issues for asp.net core and VS2019 are resolved in .2461. Great work
Could you please clarify what issues are still not fixed for you?
Thanks in advance.
New projects are generated correctly now, compile fine. I only had a problem with one of the projects ( ASP.NET Core API app) to run localhost:5000 in a browser (ERROR 404). I think one of the screenshots above shows this. But I’m not sure if it’s the Elements or .NET Core itself problem. So you can try yourself if you have the same problem running localhost:5000.
I’m running the latest VS2019 16.4.0 and .net core 3.1.
@viktoriad, didn’t we fix some issues with the launch path, specific to VS on Friday, after 2461 was built?
Does that work ok for you in Water, Artur?
I can repro the same 4o4 from VS2019, fwiw
What exactly I was suppose to check in Water?
I created ASP.NET Core API app in VS2019 and then reopened in Water and run. But I get the same error on localhost:5000 in a browser (ERROR 404).
Thanks, logged as bugs://83632
This is really as designed; and matches the C# template. Basically you want to go to
It’s an api only service.
bugs://83632 got closed with status nochangereq.
bugs://83610 got closed with status fixed.
bugs://83570 got closed with status fixed.