![]() ![]() So, now that ASP.NET Core is a viable option, when should you start upgrading your projects to use it? Here are some options and my opinion on each one. NET Core to stop being on the bleeding edge, this is your cue to start paying attention. If you’re a company who’s been waiting for. NET Core (and ASP.NET Core) have been around for a while, and there are robust, productive developer tools available to work with them. ![]() It’s been a long wait, but we’re now in a world where. There have also been some nice new improvements to the dotnet CLI, which I’ve also written about ( here and here). ![]() I was able to migrate my existing project.json-based projects to the new MSBuild project file format without issue. Visual Studio 2017 was released recently, and appears to be stable. There were also breaking changes to the project system, which was painful, but was necessary in order for Core projects to interact with every other project type in Visual Studio. However, the tooling story lagged for a while (as is typical), and while normally this wouldn’t be such a big barrier to adoption (if it were just Visual Studio), in this case the affected tooling included the dotnet CLI as well. Overall, the framework and server-side components have been pretty solid, with few major bugs reported, and a bunch of nice features added to both ASP.NET and Entity Framework Core in the 1.1 release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |