Last post Dec 21, 2016 02:23 AM by RRummel
Dec 19, 2016 08:01 PM|mellson|LINK
How is the ASP.NET core experience now? Is it good enough for a new project? Or would you still choose V4?
Dec 19, 2016 10:57 PM|Dmitry Sikorsky|LINK
I like it very much. It is fresh, fast, lightweight and easy to use. I'm using asp.net core 1.1 for new projects now. I think 4.5 is only for something large that needs IIS or windows integration etc.
Dec 20, 2016 06:45 AM|mellson|LINK
That sounds promising. When you say a large project, how large would it need to be for you to choose V4.5 instead of core?
Dec 20, 2016 07:04 AM|damienBod|LINK
ASP.NET Core 1.1 works well for large projects as well. Some of the tooling is still a bit rough, but it works well. I would not start a new project using v4.5.
Dec 20, 2016 07:05 AM|mellson|LINK
Dec 21, 2016 02:23 AM|RRummel|LINK
ASP.NET Core is NOT limited, however .NET Core is limited (I cannot remember on top of my head, however lot's of functionality are NOT available in .NET Core).
ASP.NET Core can target either .NET Core or .NET Framework.
If you are hosting on Windows anyway, you may want to write ASP.NET Core targeting .NET Framework to get access to a larger functionality.
Here is a list of situations in which your ASP.NET Core should target either .NET Core or .NET Framework (the list does not list most important functionality deficiencies in .NET Core) : https://docs.microsoft.com/en-us/dotnet/articles/standard/choosing-core-framework-server