Skip to main content

Gulp is no longer the default choice for ASP.NET Core

Today when you create an ASP.NET Core application, you will find “gulpfile.js” present in your project structure (At the time of writing this post with RC2 release). However Microsoft is making a move with task runner and Gulp is no longer the default choice for ASP.NET Core application in a future release. It’s time to say “Goodbye Gulp“. And it is replaced with a new VS extension called BundlerMinifier. Gulp will be removed from default ASP.NET Core project template, but if you wish to use then, you can add it back. Earlier, an announcement was made about Project.json going away and now its turn for Gulp.
Read More

Quick Migration guide for ASP.NET Core RTM from RC2

Quick summary of what’s changed in ASP.NET Core RC2

After a long wait, ASP.NET Core RC2 was released yesterday. Finally.. Earlier I posted about Quick summary of what’s changed in ASP.NET 5 but after that ASP.NET 5 was renamed to ASP.NET Core 1.0 and earlier this year ASP.NET team in NDC conference gave overview of what’s coming and what’s new in ASP.NET Core RC 2. And in mid April 2016 ASP.NET team gave a glimpse of ASP.NET Core RC2, when they published a sample project on github using ASP.NET Core RC2. I also covered it in my post First look at ASP.NET Core 1.0 RC2. Since RC2 is finally out, so in this post, find a quick and short summary of what’s new and what’s changed in ASP.NET Core RC2. Read More

Various ASP.NET Core Diagnostics Middleware

Various ASP.NET Core Diagnostics Middleware

Middleware is the heart of an ASP.NET Core application. You can think of middleware as small connectors which makes a pipeline to accept requests and send responses. Anything which your ASP.NET core application does is performed by middleware. Middleware are small application components that can be incorporated into an HTTP request pipeline like HttpHandlers and HttpModules. But middleware are different from HttpModules. In this post, we take a look at various ASP.NET Core Diagnostics middleware examples which are used for error logging and handling, exception handling and runtime environment information. Read More

Angular CLI is here for Angular 2

Setting up Angular 2 in your application is quite time-consuming compare to AngularJS 1. For setting up Angular 1.x, all you need to do is to just add the reference of library but with Angular 2, it requires some more work due to dependency on Grunt or Gulp for build process, TypeScript and it’s compiler. And setting this with Visual Studio 2015 is even more time-consuming. Angular Team is aware of this and they came up with a solution and introduced a new command line tool (cli) for Angular 2. Yes, Angular CLI is here for Angular 2 applications.
Read More