Last post Dec 20, 2016 04:19 PM by object ref
Dec 19, 2016 08:12 PM|object ref|LINK
I am using VS 2017 (latest RC) and .NET core 1.1 and trying to create an ASP.NET Core application. When I select the ASP.NET Core Web Application (.NET Core) project template of Visual Studio, I have a lot of problems with some Microsoft packages I want
to install/update, some are not up to 1.1 .NET Core version, some weird empty folders appears suddenly in Solution Explorer etc. Clearly, the tooling is somewhat problematic for .NET Core right now.
When I select the ASP.NET Core Web Application (.NET Framework) template, it seems that I have not any of the above issues. I now that in the later case, the runtime that runs my Web app is .NET Framework and not .NET Core.
So, strategically wised: Is it valid option to start now with .NET Core but using the ".NET Framework" project template (so to use the .NET Framework runtime), trying to not using any Windows dependencies and when tooling gets better to "move" the project
to .NET Core Runtime?
Dec 19, 2016 11:00 PM|Dmitry Sikorsky|LINK
There should be absolutely no problems to create an empty asp.net core 1.1 project that targets .net core. Maybe you could show some screenshots or provide other details in different way? It is hard to say what is wrong without additional info.
Dec 20, 2016 10:07 AM|object ref|LINK
Hi Dmitri, thank you for the reply!
Yes, I can create an empty asp.net core (.net core) empty project. But try to add a reference to package to "Microsoft.VisualStudio.Web.CodeGeneration.Tools" or try to update the package "Microsoft.NETCore.App"...These things worked just fine in v 1.0 of
.NET Core and as I see from web searches, these are side effects of the transition from project.json to the newer format. And I also have Visual Studio hangs and restarts, something that I have never had with the previous version of the tooling. And all these
problems disappear If I use the second project template, the one that target the runtime of .NET Framework and not the one of .NET Core.
Anyway, I just need to know if the strategy to target now the .NET Framework and create asp.net core apps, will pay in the future...
Dec 20, 2016 03:58 PM|bruce (sqlwork.com)|LINK
while the core 1.1 runtime is production ready, the visual studio tooling for asp.net core is only alpha, but you have couple options:
If you want core framework compatibility, I would not switch from core, its too easy to use features that will not be ported to .net standard.
Dec 20, 2016 04:19 PM|object ref|LINK
thank you for your reply!
I have used VS Code in my Mac with Yeoman with a lot of success. But I wanted to use Sql Server LocalDb and that is the reason why I messed with VS 2017 RC. I will take your suggestion and install VS Code in my Windows VM as well and use that.