Yes, you read it right. Project.JSON for ASP.NET Core is going away. One of the biggest change with ASP.NET Core 1.0 was moving towards JSON over XML for configuration settings. And Project.json is the way to define dependencies, managing your runtime frameworks, compilation settings, adding scripts to execute at different events (Prebuild, Postbuild etc.). (more…)
Earlier I posted about Cascading DropDown List using Angular 2 and in this post, we take it to next level and implement it with ASP.NET Core Web API and Angular 2. But starting/configuring AngularJS 2 with ASP.NET Core is not straightforward and it requires some manual configurations to be done. If you are not sure how to do it, I recommend you to read this helpful post to find out post how to start with Angular 2 in ASP.NET Core with TypeScript using Visual Studio 2015.
Previously I posted about what is expected in ASP.NET Core 1.0 RC2 and then posted about what’s new in ASP.NET Core 1.0 RC2. Some of the important changes from RC1 to RC2 are the introduction of new command line tool named “dotnet” to replace “dnx” and moving towards .NET Platform Standards. And I think we are now getting closer to ASP.NET Core 1.0 RC2 release as in last week ASP.NET team released a sample ASP.NET Core 1.0 RC2 project. In this post, I will take you through how to download, build and run this sample project. (more…)
ASP.NET Core prefers JSON over XML for configuration and earlier I posted about all different JSON files present in new ASP.NET Core solution. And one of the JSON configuration file is Package.json and it is the place for npm modules. But when you won’t find this file in solution explorer for your ASP.NET Core project, as by default, this file is hidden. In this short post, you will find various way to make this file visible in Solution explorer.
Earlier I posted quick summary of what’s changed in ASP.NET Core and one of the biggest change is Introduction of middleware. If you are coming from ASP.NET background then you should be aware about HTTPHandlers and HTTPModules. Middleware are replacement of these things. It’s a new and cleaner approach to play with HTTP pipeline. Read my post How ASP.NET Core 1.0 Middleware is different from HttpModule.
Along with built-in middleware, there are 2 options to define inline middleware using
app.Run extension methods. And if you are currently working and playing with ASP.NET Core 1.0 then you may find examples of
configure() method of Startup.cs class. Both of them are used for same purpose but they are different. How?