We will be supporting two different versions of .NET Core because Microsoft is developing two different versions: “Long Term Support” (LTS) and “Fast Track Support” (FTS).

LTS (the 1.0.3 version) is focused on stability and use on production sites, so its development will take place more slowly. FTS (the 1.1 version) is the latest and greatest version, with more new features, but potentially more new issues as well. We don’t recommend it for use on production sites, but it’s there for you to tinker with and check out the latest Core features.

We’ll always support the latest LTS and FTS versions, with the priority given to the more stable LTS versions that are intended for production. The versions run side by side, so you can use whichever you choose (or use both for different purposes).

We’ve run in to some issues already where the latest Visual Studio version supports later (newer) versions than our servers support. That is going to continue to happen from time to time, because it isn’t feasible for us to keep up with the FTS versions across all of our production servers. The development cadence is too quick. What we will probably do with Core from this point on is update quarterly. We’ll try to post in the forum when we make those updates.

Note that .NET Core is only available on the Windows 2012 servers. If your site is running on a Windows 2008 server you’ll have to migrate to a 2012 server to use .NET Core. We can do the migration for you, just contact support and we’ll take it from there.

I see this post has been washed up. The whole thing is misleading. You installed 1.1.0 but developers are offered 1.1 as 1.1.1 in VS, and there is n way to build using 1.1.0. so the point n “installing 1.1” is moot.
So when is it I can deploy 1.1 code at my site?
Or dyou have a suggestion to compile using 1.1.0 when using isua Studio?

Hi Gerard. The rapid development cycle that Microsoft is using for .NET Core leaves us at a bit of a disadvantage. It isn’t feasible to update dozens of production servers every few weeks when they release new builds (we have to test them first to see what’s involved in the update, because they keep changing the way it works), so we have to come up with an update schedule that’s reasonable for us. It looks like that will be quarterly, and our next update will be some time in June (I’ll post dates when I find out what they are).