Migrating to asp.net MVC Core
When we create ERP web applications, we often choose ASP.net technology over PHP or other technologies. ASP.net MVC Core is the new cross-platform(Windows, Mac, Linux OS) development framework from Microsoft. ASP.net Core is based on the same principles you've used in ASP.net MVC, There are so-many improvements in the framework and tooling, some are revolutionary. The best way to learn new technologies is by comparing it with the old and finding out what has changed. The basic of Model View Controller architecture still remains the same and we can say that from coding perspective there aren't many changes, but there are framework level changes, project structure changes, hosting and deployment changes and many more. So let’s dive in.
ASP.net MVC Core improvements
AXL’s course on ASP.NET core is excellent course to understand its features.
ASP.net MVC Core improvements
- Cross-platform (Windows, Mac, Linux OS)
- Built on .NET Core, which supports true side-by-side app versioning
- New tooling that simplifies modern Web development
- Single aligned web stack for MVC and Web API
- Cloud-ready environment-based configuration
- Integrated support for creating and using NuGet packages
- Built-in support for dependency injection
- Ability to host on IIS or self-host in your own process
Despite the fact that Rebuilt from the ground up, efforts have been made to make migration as painless as possible. More than 90% of what you learn is the same in the new ASP.net Core. As a developer, you will notice the following differences:
- Solution Structure Changes
There is no Web.config and Global.asax. Project.json and appsettings.json deals with configuration settings, authentication and application start specific code execution. The new Project.json file defines dependencies, build and publish setup, etc. instead of .csproj file. - wwwroot is now place for static files
The wwwroot folder represents the actual root of the web app when running on a web server. Static files like config.json, which are not in wwwroot will never be accessible, and there is no need to create special rules to block access to sensitive files. - ASP.NET Core apps doesn’t need IIS for hosting
- User SecretsFor handling sensitive data during our development work
- Roslyn compiler for compiling code dynamically. Now there is no need to compile your code, on any code changes that you make.
- No dll by default.
- Everything is Nuget package in Core MVC. Bundling and minification is done using Grunt or Gulp, unlike defining bundles in BundleConfig file.
- Manage client side dependencies via NPM and Bower.
- It also support RESTful style routes with attribute routing
- New controller and action tokens.
- These tokens allows you to reference controller and action names in the route template.
AXL’s course on ASP.NET core is excellent course to understand its features.
Comments
Post a Comment