.NET Core January 2018 Update #1199

leecow · 2018-01-09T19:17:11Z

.NET Core January 2018 Update

The .NET Core January 2018 Update is available. This release includes:

.NET Core 1.0.9, 1.1.6 and .NET Core SDK 1.1.7
.NET Core 2.0.5 and .NET Core SDK 2.1.4

You can read about the updates in the .NET Core release notes.

Please report any issues you find with the January 2018 Update, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:

dotnet/cli - for CLI tools and questions
dotnet/corefx - for API issues and questions
dotnet/coreclr - for runtime issues
dotnet/core-setup - for installer issues
nuget/home - for NuGet questions and issues

nulltoken · 2018-01-11T16:16:35Z

⚠️ This may not be the best place to report this. I'd be happy to open a new issue in another repository would anyone point me in the right direction.

Is there any timeline to see this update deployed on VSTS Hosted VS2017 agents?

Updating the global.json file with the new version leads to such errors in the build logs.

2018-01-11T15:46:38.5191512Z Building...

2018-01-11T15:46:38.9108647Z ##[error]The specified SDK version [2.1.4] from global.json [D:\a\1\s\global.json] not found; install specified SDK version

Did you mean to run dotnet SDK commands? Please install dotnet SDK from:

  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

 

2018-01-11T15:46:38.9133781Z

2018-01-11T15:46:40.8355697Z ##[error]An error occured...

Taking a look at the latest published content of the Hosted VS2017 agent software inventory, it looks like the latest deployed version of .NET Core is 2.0.3.

Petermarcu · 2018-01-11T16:26:29Z

@livarcocc may be able to get the right people to answer that. Are you using global.json because you want to force yourself to a specific SDK and not just use the latest that VSTS has?

Chris197 · 2018-01-11T16:53:21Z

If I want to apply this new version to an existing installation using IIS on Windows Server, do I need to install the Windows Hosting Bundle or is that only required on first setup? Sorry if this has been asked before, I couldn't find the answer.

livarcocc · 2018-01-11T17:36:53Z

@joeloff to comment on the hosting bundle. But if you are trying to use the SDK on Windows Server, I would say it should be ok to just install the latest released SDK.

I will also try to find the right person regarding the version in VSTS. @leecow in case he can help here.

joeloff · 2018-01-11T17:45:14Z

You should consider updating the hosting bundle as the new one carries the package store for 2.0.5 as well as the 2.0.5 runtime. Additionally it has a newer version of ANCM for IIS as well. The hosting bundle though doesn't carry the SDK, so if you had a previous version of the SDK on the machine you'll probably want to update that separately.

Are you using the machine as a development environment? VS carries a copy of ANCM as well, but because the changes in ANCM for this release impacts hosting applications in IIS, VS was not updated with a new copy of ANCM.

nulltoken · 2018-01-11T19:04:50Z

I will also try to find the right person regarding the version in VSTS. @leecow in case he can help here.

@Petermarcu @livarcocc Thanks!

Chris197 · 2018-01-12T11:08:34Z

@joeloff , @livarcocc, Not using the machine for development, so I will install the hosting bundle to make sure all is up to date, thanks!

TomCJones · 2018-01-13T05:34:37Z

just tried to host a web app - it seems to always use port 5000 no matter what port I put in launchsettings.json. I tried to different solutions, one brand new.

Petermarcu · 2018-01-13T05:52:46Z

@Eilon @DamianEdwards

Eilon · 2018-01-16T02:31:42Z

@TomCJones - can you share more info about your setup? If you could upload a repro app to GitHub that would be ideal, but otherwise please share your launchSettings.json, appsettings.json, Program.cs, Startup.cs, and other relevant files. It could be that an environment variable or other config setting is overriding your desired port value.

TomCJones · 2018-01-16T03:50:18Z

sorry for the confusion, I didn't read the instructions carefully enough. They are kind of dense.

bording · 2018-01-16T22:21:16Z

I originally posted this in the SDK repo (dotnet/sdk#1849), but it appears that there was a regression on some of the bundled templates in 2.14.

2.1.3

microsoft.dotnet.common.itemtemplates.1.0.0-beta3-20171117-314.nupkg
microsoft.dotnet.test.projecttemplates.2.0.1.0.0-beta3-20171117-314.nupkg

2.1.4

microsoft.dotnet.common.itemtemplates.1.0.0-beta3-20171110-312.nupkg
microsoft.dotnet.test.projecttemplates.2.0.1.0.0-beta3-20171110-312.nupkg

Was this intentional?

livarcocc · 2018-01-16T22:25:50Z

@mlorbetske to confirm the version that should be used!

mlorbetske · 2018-01-16T22:53:20Z

While this wasn't an intentional change (the move back to 312), the only impact here should be that the root namespace wouldn't be included in vbproj files for test projects (as it would have been introduced in build 313 which failed due to some CI issues which were corrected with 314) - the item templates should contain no differences.

christiansk · 2018-01-21T20:29:47Z

I installed the updates and can see version 2.0.5 in the command prompt using "dotnet --version", but VS2017 still shows the previous SDK version in my projects. I can see package Microsoft.NETCore.App 2.0.5 in NuGet but it won't let me update saying the version is "blocked by project". How can I upgrade my project in VS to develop against the latest version?

Petermarcu · 2018-01-21T23:20:34Z

@leecow are the runtime and SDK versions mismatched in the original post?

.NET Core 1.0.9, 1.1.6 and .NET Core SDK 2.1.4
.NET Core 2.0.5 and .NET Core SDK 1.1.7

I think it should be 2.X with 2.X and 1.X with 1.X.

Petermarcu · 2018-01-21T23:21:39Z

@christiansk , I believe you need the SDK version 2.1.4 in order to have VS support targeting 2.0.5. dotnet --version should say 2.1.4 if you have the right SDK installed.

christiansk · 2018-01-21T23:57:51Z

@Petermarcu You are correct, it says 2.1.4 - I confused the SDK/runtime versions in my previous comment. Sorry about that. Still, I have it installed and can't get VS to allow me to update the SDK dependency. Any clue as to what else could cause the Microsoft.NETCore.App package to be "locked" to 2.0.0?

Petermarcu · 2018-01-22T00:33:29Z

Here are a few things to note.

By just installing 2.0.5, all your tools and applications that were running on shared 2.0.0 runtime will now run on 2.0.5.
2.0.5 is not "targetable" per se. It doesn't have any new API's, just bug fixes.

So just by installing the 2.1.4 SDK, when you do things like dotnet run a 2.0.0 application, it will automatically run on 2.0.5.

If you are doing a self-contained application, you need to explicitly set the version of the runtime you want with your application. This can be done by adding <RuntimeFrameworkVersion>2.0.5</RuntimeFrameworkVersion> to your project in a PropertyGroup.

Hope this helps.

christiansk · 2018-01-22T02:29:49Z

Got it. Thanks!

leecow · 2018-01-22T19:06:03Z

@Petermarcu , @christiansk - sorry about the version scrambling. Fixed!

cgountanis · 2018-03-14T14:01:14Z

So 2.1.4 was removed and replaced with 2.1.101?

livarcocc · 2018-03-14T16:18:45Z

2.1.101 is now the latest release of the .NET Core SDK.

You can still obtain the 2.1.4 from the all downloads link here: https://www.microsoft.com/net/download/all.

cgountanis · 2018-03-14T16:28:31Z

It is not there, I don't need it just wondering why the version went down on the SDK and up on the runtime?

Petermarcu · 2018-03-14T16:31:01Z

Because we are realigning major and minor for the runtime and sdk.

DamianEdwards · 2018-03-14T16:34:56Z

2.1.101 is a higher version than 2.1.4
The numbers in each part are whole numbers, not fractions, so the 101 is > 4

cgountanis · 2018-03-14T17:37:19Z

Dah, thank you. 🤯

Petermarcu · 2018-03-18T16:51:29Z

Closing this one in favor of the latest announcement: #1341

leecow added the announcement label Jan 9, 2018

Petermarcu mentioned this issue Feb 21, 2018

.NET Core December 2017 Update #1172

Closed

Petermarcu closed this as completed Mar 18, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

.NET Core January 2018 Update #1199

.NET Core January 2018 Update #1199

leecow commented Jan 9, 2018 •

edited

Loading

nulltoken commented Jan 11, 2018

Petermarcu commented Jan 11, 2018

Chris197 commented Jan 11, 2018

livarcocc commented Jan 11, 2018

joeloff commented Jan 11, 2018

nulltoken commented Jan 11, 2018

Chris197 commented Jan 12, 2018

TomCJones commented Jan 13, 2018

Petermarcu commented Jan 13, 2018

Eilon commented Jan 16, 2018

TomCJones commented Jan 16, 2018

bording commented Jan 16, 2018

livarcocc commented Jan 16, 2018

mlorbetske commented Jan 16, 2018

christiansk commented Jan 21, 2018 •

edited

Loading

Petermarcu commented Jan 21, 2018

Petermarcu commented Jan 21, 2018

christiansk commented Jan 21, 2018 •

edited

Loading

Petermarcu commented Jan 22, 2018

christiansk commented Jan 22, 2018

leecow commented Jan 22, 2018

cgountanis commented Mar 14, 2018

livarcocc commented Mar 14, 2018

cgountanis commented Mar 14, 2018 •

edited

Loading

Petermarcu commented Mar 14, 2018

DamianEdwards commented Mar 14, 2018

cgountanis commented Mar 14, 2018

Petermarcu commented Mar 18, 2018

.NET Core January 2018 Update #1199

.NET Core January 2018 Update #1199

Comments

leecow commented Jan 9, 2018 • edited Loading

.NET Core January 2018 Update

nulltoken commented Jan 11, 2018

Petermarcu commented Jan 11, 2018

Chris197 commented Jan 11, 2018

livarcocc commented Jan 11, 2018

joeloff commented Jan 11, 2018

nulltoken commented Jan 11, 2018

Chris197 commented Jan 12, 2018

TomCJones commented Jan 13, 2018

Petermarcu commented Jan 13, 2018

Eilon commented Jan 16, 2018

TomCJones commented Jan 16, 2018

bording commented Jan 16, 2018

livarcocc commented Jan 16, 2018

mlorbetske commented Jan 16, 2018

christiansk commented Jan 21, 2018 • edited Loading

Petermarcu commented Jan 21, 2018

Petermarcu commented Jan 21, 2018

christiansk commented Jan 21, 2018 • edited Loading

Petermarcu commented Jan 22, 2018

christiansk commented Jan 22, 2018

leecow commented Jan 22, 2018

cgountanis commented Mar 14, 2018

livarcocc commented Mar 14, 2018

cgountanis commented Mar 14, 2018 • edited Loading

Petermarcu commented Mar 14, 2018

DamianEdwards commented Mar 14, 2018

cgountanis commented Mar 14, 2018

Petermarcu commented Mar 18, 2018

leecow commented Jan 9, 2018 •

edited

Loading

christiansk commented Jan 21, 2018 •

edited

Loading

christiansk commented Jan 21, 2018 •

edited

Loading

cgountanis commented Mar 14, 2018 •

edited

Loading