From .NET 4.6.1 to .NET Core
In this post, I’ll discuss the process I took to go from the dotnet new command all the way to a single page application which sends GET requests, parses the responses and uses Angular2 to display rich, human readable versions of the parsed data
The final part in our multi-post exploration of the major bundling options available for .NET Core.
This week we touch on certain design decisions that went into the .NET Core 1.0 tooling release, how bundling is a design time action, why Gulp wasn’t included in the official tooling (at .NET Core’s epoch anyway), and how to bundle with Gulp.
The second part in our multi-post exploration of the major bundling options available for .NET Core.
This week we’ll take a look at the bundling option that Mads Kristensen created specifically for .NET Core: Bundlerminifier.Core, which is based on his BundlerMinifier project.
The first part in our multi-post exploration of the major bundling options available for .NET Core.
This week we’ll go into a little about what bundling is and why you wold use it, before taking a look at how to use webpack to bundle all of your client side dependencies into graphs. We’ll also touch (very briefly) on TypeScript, too.
.NET Core supports many different types of project templates.
This week, I thought I would go through the major project templates available in version 1.0 of the .NET Core SDK, giving a brief explanation of each.
Sometimes you just want to build a website with strong separation of concerns – that’s where the MVC model can help.
This week we build an MVC application, go through what an MVC application is (covering separation of concerns, too), where you might use one, and what some of the most important configuration options are and where to find them.
![[dotnet new] Angular Single Page Application - Setup and How The Template Works](https://i0.wp.com/dotnetcore.gaprogman.com/wp-content/uploads/2017/04/Angular-Single-Page-Application-Header-Image.jpg?resize=40%2C40&ssl=1){kind=small}
