Configuration Providers

NOTE: This article has been edited 16-10-2015 to line up with ASP.NET 5 beta8 latest changes Application configuration so common task that designers of new .NET decided that it will be one of the central components. There are many configuration providers available to use out of the box with DNX. Configuration is loaded as a hierarchy and programmer has control over the sources and the order of loading process. This comes in handy as a standardized way of handling repeatable task. With feature complete 1.0.0-beta8 release I feel that it is the right time to take a closer look at

Hacking DNX. Part two – debugging DNU utility

In part one I described how to prepare for debugging DNX. This part is focused on understanding and debugging DNU – the tool delivered with each DNX used to develop, build, pack and publish .NET projects. This is part two of my series Hacking DNX. Agenda [may change a bit]: Build & first debug session Debugging DNU Utility (this) Overview of DNX projects and architecture DNX internals Understanding DNU First and foremost to understand is that DNU utility is just a wrapper for running various commands from Microsoft.Dnx.Tooling.dll via DNX. For example:

translates to: To understand more about
Hacking DNX. Part one – build & debug

This is part one of my first series Hacking DNX. Agenda [may change a bit]: Build & debug (this) Debugging DNU Utility Overview of DNX projects and architecture DNX internals So you like diving deep into code? Or maybe trying to solve problem with new ASP.NET 5 on your own?. After all code is the source of truth. Read on to see how to compile and run your very own version of DNX. First of download source code of dnx using git client

One thing to remember is to include –recursive flag to include sub projects as well. If