From bce436c8d97b6005f425e922d31924a99108c75f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henning=20St=C3=B8verud?= Date: Fri, 23 Oct 2015 10:26:08 +0200 Subject: [PATCH] Default name changed from config.json to appsettings.json In beta 8 the name of the genrated config file has changed from config.json to appsettings.json. --- aspnet/tutorials/your-first-aspnet-application.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/tutorials/your-first-aspnet-application.rst b/aspnet/tutorials/your-first-aspnet-application.rst index dacef6e0c5..dc4bb4f4a6 100644 --- a/aspnet/tutorials/your-first-aspnet-application.rst +++ b/aspnet/tutorials/your-first-aspnet-application.rst @@ -35,7 +35,7 @@ At this point, the project is created. If you are prompted to select a source co Looking at the Solution Explorer and comparing the elements with what we're familiar with in previous versions of ASP.NET, a few things stick out as being new and different. There's now a ``wwwroot`` folder, with its own icon. Similarly, there's a *Dependencies* folder **and** still a *References* folder - we'll discuss the differences between these two in a moment. Rounding out the list of folders, we have Controllers, Models, and Views, which make sense for an ASP.NET MVC project. This template also includes a Services folder, initially holding MessageServices used by ASP.NET Identity, and a Migrations folder, which holds classes used by Entity Framework to track updates to our model's database schema. -Looking at the files in the root of the project, we may notice the absence of a few files. Global.asax is no longer present, nor is web.config, both mainstays from the start of ASP.NET. Instead, we find a Startup.cs file and a config.json file. Adding to this mix are bower.json, gulpfile.js, package.json, and project.json (the Project_Readme.html file you can see in the browser tab). Clearly the success of Javascript in web development has had an effect on how ASP.NET 5 projects are configured, compiled, and deployed, with JavaScript Object Notation (JSON) files replacing XML for configuration purposes. +Looking at the files in the root of the project, we may notice the absence of a few files. Global.asax is no longer present, nor is web.config, both mainstays from the start of ASP.NET. Instead, we find a Startup.cs file and an appsettings.json file. Adding to this mix are bower.json, gulpfile.js, package.json, and project.json (the Project_Readme.html file you can see in the browser tab). Clearly the success of Javascript in web development has had an effect on how ASP.NET 5 projects are configured, compiled, and deployed, with JavaScript Object Notation (JSON) files replacing XML for configuration purposes. While we're at it, you may not notice it from the Solution Explorer, but if you open Windows Explorer you'll see that there is no longer a .csproj file, either. Instead you'll find an .xproj file, an MSBuild file that serves the same purpose from a build process perspective, but which is much simpler than its csproj/vbproj predecessor.