Add note to tutorial about being written for ASP.NET MVC 4, and minor changes to ASP.NET Core getting started page. References #300

Author: Daniel15

site/jekyll/getting-started/aspnet5.md renamed to site/jekyll/getting-started/aspnetcore.md

@@ -1,36 +1,36 @@
 ---
-id: aspnet5
+id: aspnetcore
 layout: docs
-title: Getting Started on ASP.NET 5
+title: Getting Started on ASP.NET Core
 ---
 
-Getting started with ReactJS.NET on ASP.NET 5 and MVC 6 requires a few more steps compared to previous versions of ASP.NET and MVC. A more fully featured tutorial will be released once the stable release of ASP.NET 5 is out.
+Getting started with ReactJS.NET on ASP.NET Core requires a few more steps compared to previous versions of ASP.NET and MVC. A more fully featured tutorial will be released soon.
 
-Note that ASP.NET 5 is still in beta, and so there may still be some sharp edges. ReactJS.NET requires at least Visual Studio 2015 and ASP.NET 5 **Beta 8**. Additionally, ReactJS.NET does not support the Core CLR at this point in time, so you will need to ensure your project is not referencing it. Remove the `"dnxcore50": { }` line from your `project.json` file.
+ReactJS.NET requires Visual Studio 2015 and ASP.NET Core RTM (final release). Additionally, ReactJS.NET does not support .NET Core at this point in time, so you will need to ensure your project is not referencing it. If you're creating a new website, use the "ASP.NET Core Web Application (.NET Framework)" project template. Otherwise, make sure your `project.json` references `net452` in its `frameworks` section, **not** `netcoreapp`.
 
-Once this has been removed, install the `React.AspNet` package through NuGet. After the package is installed, ReactJS.NET needs to be initialised in your `Startup.cs` file (unfortunately this can not be done automatically like in previous versions of ASP.NET with WebActivator). At the top of the file, add:
+Install the `React.AspNet` package through NuGet. After the package is installed, ReactJS.NET needs to be initialised in your `Startup.cs` file (unfortunately this can not be done automatically like in previous versions of ASP.NET with WebActivator). At the top of the file, add:
 ```
 using React.AspNet;
 ```
 
 Directly above:
 
 ```csharp
-// Add MVC services to the services container.
+// Add framework services.
 services.AddMvc();
 ```
 
 Add:
 
 ```csharp
+services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
 services.AddReact();
 ```
 
 
 Directly **above**:
 
 ```csharp
-// Add static files to the request pipeline.
 app.UseStaticFiles();
 ```
 

site/jekyll/getting-started/tutorial.md

@@ -4,6 +4,10 @@ title: Tutorial
 layout: docs
 ---
 
+> Note:
+>
+> This tutorial was written for Visual Studio 2013 and ASP.NET MVC 4, and will be updated to Visual Studio 2015 and ASP.NET Core in the near future.
+
 This tutorial covers the end-to-end process of creating a brand new ASP.NET MVC website and adding a React component in it. We will start from scratch and end with a fully functioning component. It assumes you have basic knowledge of ASP.NET MVC and using Visual Studio. This tutorial is based off the [original React tutorial](http://facebook.github.io/react/docs/tutorial.html) but has been modified specifically for ReactJS.NET.
 
 We'll be building a simple, but realistic comments box that you can drop into a blog, a basic version of the realtime comments offered by Disqus, LiveFyre or Facebook comments.

site/nginx.conf

@@ -7,9 +7,11 @@ server {
 	rewrite ^/download$ /getting-started/download.html redirect;
 	rewrite ^/docs$ /getting-started/download.html redirect;
 
-	rewrite ^/packages/(.*)$ https://ci.appveyor.com/nuget/reactjs.net/$1 permanent;
+	# Old documentation URLs
+	rewrite ^/getting-started/aspnet5.html$ /getting-started/aspnetcore.html permanent;
 
 	# Old package URLs
+	rewrite ^/packages/(.*)$ https://ci.appveyor.com/nuget/reactjs.net/$1 permanent;
 	rewrite ^/dev/packages/(.*)$ https://ci.appveyor.com/nuget/reactjs.net/$1 permanent;
 
 	# Far future expires header for combined assets
@@ -33,4 +35,3 @@ server {
 		fastcgi_param HTTP_X_METHOD_OVERRIDE $request_method;
 	}
 }
-