We Keep Coding

What is the correct order of installation for running a DotNet Core web application on a local IIS server?

I run a local IIS Server with a DotNot Core 2.1 application deployed to it. I like to keep up to date with the latest security patches that are released monthly and I use the Core download page to do so.
My question is, what ALL do I need to install each time and in what order. I usually find a Framework installer and I chose the SDK just to make I have everything. Then I find a ASPNET.CORE installer and I run those in. Finally, I run the Web Hosting Bundle.
Am I doing too much? Do some of these items copy over the same assets? What is the correct proceedure?

If you need to host an asp.net core web app, follow the Host ASP.NET Core on Windows with IIS Guide.
In terms of installing things, follow the Install the .NET Core Hosting Bundle Section
The bundle will install 3 things:
.NET Core Runtime
.NET Core Library
ASP.NET Core Module (for IIS)

Migrate a Cloud Service Web Role to Service Fabric with Storage Dependencies

Following this guide from Microsoft, it seems fairly straightforward to migrate web and worker roles to service fabric. This picture specifically shows how you can still use Azure Storage from Service Fabric apps.
Since web roles must be .net core on service fabric, this requires that the storage sdk support .net core but I have been unable to find libraries that are compatible. There seems to be a storage preview package that does support netstandard1.6 but it's dependencies do not.
Has anyone gotten this to work? Basically, I'm looking for a storage package or configuration that will work with .net core so that I can use Azure storage from a asp mvc core app.

ASP.NET Core web applications don't actually need to be compiled against .NET Core - these are two separate things. In fact the Service Fabric SDK itself is still full .NET Framework. The terminology is confusing (we're bad at naming things).
"ASP.NET Core" is the name of the latest ASP.NET product that Service Fabric supports.
You can build an ASP.NET Core application against either .NET Core or .NET Framework. In Visual Studio, if you create a new project under C# -> Web, you'll see ASP.NET Core options for both .NET Core and .NET Framework.
On Service Fabric, currently, you should use ASP.NET Core built against .NET Framework, not .NET Core. In Visual Studio again, if you create a new project under C# -> Cloud -> Service Fabric Application, you'll have the option of adding an ASP.NET Core service - this will be created using full .NET Framework.

Hosting ASP.NET Core application on shared Linux hosting

Now asp.net core has been released so we can develop/deploy .net application on any platform.
I am trying to play with asp.net core and able to run my application on ubantu os(On Virtual Machine). But i just wanted to hosted dot net core application on shared linux hosting environment where simply upload published file.
I was following Tony's blog, to play with core.
We need DNVM, DNU and DNX to run application, but we don't have terminal to execute these commands on shared hosting.
Help me figure out the solution.

It is somewhat possible... and actually, Scott Hanselman just did it using .NET Core 2.1 (still in preview, although). He got it running on GoDaddy's shared Linux plan. You may follow his step by step here, but you are strongly adviced not to do it.

Azure Mobile Services & Newtonsoft.Json 7

I recently upgraded Newtonsoft.Json in my project from version 6(.0.6) to 7(.0.1).
When i tried to publish the project to Azure i got an unhealthy service and the following message in the Logs:
ERROR
Found conflicts between different versions of the same dependent
assembly 'Newtonsoft.Json': 6.0.0.0, 7.0.0.0. Please change your
project to use version '6.0.0.0' which is the one currently supported
by the hosting environment.
Does that mean that azure doesn't support Newtonsoft.Json 7, or am i doing something wrong? Have i forgot something? If azure doesn't support version 7 is there a workaround? I must use thath version because i am trying to install a 3rd party package that requires it.

Azure Mobile Services has specific hosted versions of its NuGet packages and dependencies and does its own binding redirects at runtime. Unfortunately, this means you have to use Newtonsoft 6.0.4. This is specified as a dependency in the nuspec for WindowsAzure.MobileServices.Backend: https://www.nuget.org/packages/WindowsAzure.MobileServices.Backend/
What I recommend instead is that you use Azure Mobile Apps which removes this limitation. Mobile Apps is still in preview, but we recommend that customers building a new app start here. Mobile Apps is part of App Service and provides all of the benefits of that platform, such as VNET/VPN, backup and restore, more scale options, more CI options, WebJobs, etc.

Where to configure Razor page language version to C# 6?

Recently I've tried to use some C# 6 new feature (interpolated strings) in my ASP.NET MVC (5) .cshtml view, but when running got an error message complaining about the $. It is clear the compiler in C# 5 compatibility mode, or worst it is a C# 5 compiler.
When in editor a popup warning warns me (I do not know it is VS or ReSharper) Feature 'Interpolated strings' is not available in C# 5. Please use language version 6 or greater.
The project itself was set to C# 6, and I can use C# 6 features in my build time compiled code like controllers etc.
Q: Where should I set page compiler version, and will this C# 6 compiler available when I deploy my web app to Azure there?

From String interpolation in a Razor view?:
This only works in MVC6. Alternatively, also from a comment on this link, you'll need to add the roslyn code dom package from ASP.Net.
<div>
#($"Hello {this.Model.SomeProperty}")
</div>
As far as Azure is concerned, please see this link. http://azure.microsoft.com/blog/2015/08/11/update-on-net-framework-4-6-and-azure/
With great power… The tooling, framework and Azure platform teams want
to ensure the powerful tools we give you to help build your dream is
matched by the responsibility we recognize we have to keep it running
in the cloud. At the time of the Visual Studio and Azure SDK 2.7
releases, Framework 4.6 wasn’t supported broadly throughout Azure.
This is due in large part to the fact that just as many teams (or
more) are responsible for the ongoing development and stability of the
Azure platform.
For now, we have an update on the availability of .NET Framework 4.6
for Azure App Service and an article demonstrating how to get .NET
Framework 4.6 working in your Cloud Service roles.
Azure IaaS
For customers using Azure’s Infrastructure as a Service
(IaaS) services, installation of .NET Framework 4.6 is manual. To
install .NET Framework 4.6 on an Azure IaaS virtual machine, the
process is as simple as logging into the virtual machine using Remote
Desktop. Once on the machine, the .NET Framework 4.6 installer can be
downloaded and installed directly onto the virtual machine. Customers
using Azure Automation could also choose to automate the installation
onto Azure virtual machines using PowerShell.
Azure App Service
Update The Azure App Service team is nearing the end
of the testing phase for .NET Framework 4.6 and planning the
deployment to the environments. Currently, the plan is to roll out the
updates to Azure App Service during August 2015.
Azure Cloud Services
Saurabh Bhatia authored an article in the Azure
documentation center outlining how to install the .NET Framework in a
Cloud Service Role. The content has been recently updated to include
commentary specific to .NET Framework 4.6. You can find the updated
article here on the Azure documentation center.

For me installing the Microsoft.CodeDom.Providers.DotNetCompilerPlatform NuGet package solved the problem.