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 dotnet new command has support for project templates, and one of the template packages that Microsoft has released contains a collection of Single Page Applications.
In this post, I’ll take us through how to make a new project from the Angular2 template, what changes where made the .NET Core to make some of the more impressive things in this template work, and how it all fits together.In this post, I talk you through how to create an Angular2 Single Page Application from one of these templates and how it all fits together.
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.
In which my friend, all around great guy, and React guru Zac Braddy shows you how to connect to a .NET Core WebApi