ASP.NET 5 (formerly known as ASP.NET vNext), along with .NET Core, is Microsoft’s ground-up rewrite of the .NET Framework. It is designed specifically for modern cross-platform web-application development and involves a number of breaking changes and new concepts that the .NET developer will need to be aware of.
The first major change that most developers will notice straight away is that there is are more *.config files. ASP.NET 5 does away with xml based configuration files, replacing them with a JSON based approach. For example web.config has been replaced by config.json. Another key change, is that we now have access to environment variables as part of our configuration. This in itself is a major departure from the traditional ASP.NET model, and one which does require some careful consideration.
The next major change is the increase in the number of package managers that you now need to be aware of. Gone are the days where all of your ASP.NET application dependencies are managed by NuGet. ASP.NET 5 has a more defined separation of your backend dependencies and your frontend dependencies.
NuGet: For .NET Framework and .NET packages (Backend)
Node Package Manager (NPM): For frontend build dependencies (Frontend)
Bower: For client side frameworks & libraries (Frontend)
Front end build automation / task runners
ASP.NET 5 makes some significant changes to the classic project structure that we are all familiar with. The largest change is the introduction of the wwwroot folder, which is where all of your static assets are stored and served from, files outside of the wwwroot folder are inaccessible. This change provides a higher degree of separation between files that need to be served to a requesting client and your server side code. The wwwroot folder is mapped directly as the root folder of your deployed application.
Would you like to learn more about ASP.NET 5?
SSW Dev Superheroes Adam Stephensen and Duncan Hunter will be covering this and more in their two day ASP.NET 5 and Angular Superpowers Tour. Stopping in Melbourne (16th – 17th March) Brisbane (21st – 22nd March) and Sydney (31st March – 1st April).
Adam Stephensen: Hi. I’m Adam Stephensen. I’m a solution architect at SSW and the principle mentor at FireBootCamp.
I’ve just finished my first application using Visual Studio 2015, MVC-6, and AngularJS. I’m so excited to building enterprise web apps leveraging all the front end best practices developed by the java-script community, and using my C-sharp, MVC, and Web API skills for the back end, and doing it all with the productivity of Visual Studio.
I’ve got to say, though, there’s definitely a lot of pain involved. Moving to MVC-6 and Visual Studio 2015 is a massive change. It’s as big a change as changing from Web Forms to MVC. There’s a lot of new concepts to get your head around, technologies to learn, and best practices to discover.
There are major changes to the solution structure which we will have a look at in a future video. We used to have XML config files. These are gone now. In their place we’ve got JSON based config files. For example, web.config has been replaced by config.json. We only use NuGet now for getting .net framework base packages. We use Bower for funding packages, and NPM for no packages.
Now instead of getting [inaudible 00:01:08] library’s like twitter boot stamp or NuGet, we use Bower as a client style package manager. To add clients on packages we simply add them to bower.json. The other package managing you need to get your head around is NPM, no package manager. We use packages.json to configure which no packages were going to use for tasks like bundling, minification, compiling type script and less, and other frontend build processes.
Okay, yeah. It’s all a bit much. It took us weeks of working with the new stack to work out how everything fit in together, and our best practice is still evolving. But we want to help you out by sharing what we’ve learned so far. So stay tuned, and we’ll be putting together lots of great content to help you get up to speed as easily as possible, and get shipping awesome apps on the lines of technologies.
Thanks for listening, and please drop me a tweet with your feedback.
About the speakers
Adam Stephensen is a Solution Architect at SSW with a decade of experience performing needs analysis, designing and building scalable, database-driven, distributed enterprise solutions incorporating web and windows interfaces.
It’s important for anyone involved to know the basic video editing terms to keep feedback clear and concise.
Please don’t say just ‘Hello’ in chat. It’s as if you called someone on the phone and said “Hi!” and then put them on hold!
Phones have ruled our digital experience for over a decade. But where will we go for information and how will we expect it to be delivered?
This session will cover Sammy’s 3-year journey of starting in a small company and building it to become a multi-award winning organisation
After COVID the world was forced to exist remotely. Will it be the way all companies move forward into the future of business?
When asking for changes to be made to any file like a web page, Word document, PowerPoint slide, or code, always include the original version of the content (“X”) together with the changes you require (“Y”).
Are you about to embark on a new Azure project? Do you want to know how much it’ll cost to run? And everyone needs to get the cost down on their current project. Right? 💸
Can we save costs and future proof our products? Let’s use Power Apps and new development strategies.
Running events is a challenge. And making sure your speakers and attendees are happy is an even bigger task. Adam and Jakob discuss keeping conferences interesting and adding value to future events.
App modernisation can be daunting task and could include unnecessary technical debt. Let’s find out how we can navigate the future.