New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Core January 2018 Update #1199

Closed
leecow opened this Issue Jan 9, 2018 · 28 comments

Comments

Projects
None yet
@leecow
Member

leecow commented Jan 9, 2018

.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:

@leecow leecow added the Announcement label Jan 9, 2018

@nulltoken

This comment has been minimized.

Show comment
Hide comment
@nulltoken

nulltoken Jan 11, 2018

⚠️ 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.

nulltoken commented Jan 11, 2018

⚠️ 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

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Jan 11, 2018

Member

@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?

Member

Petermarcu commented Jan 11, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@Chris197

Chris197 Jan 11, 2018

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.

Chris197 commented Jan 11, 2018

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

This comment has been minimized.

Show comment
Hide comment
@livarcocc

livarcocc Jan 11, 2018

Member

@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.

Member

livarcocc commented Jan 11, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@joeloff

joeloff Jan 11, 2018

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.

joeloff commented Jan 11, 2018

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

This comment has been minimized.

Show comment
Hide comment
@nulltoken

nulltoken Jan 11, 2018

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

@Petermarcu @livarcocc Thanks!

nulltoken commented Jan 11, 2018

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

This comment has been minimized.

Show comment
Hide comment
@Chris197

Chris197 Jan 12, 2018

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

Chris197 commented Jan 12, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@TomCJones

TomCJones Jan 13, 2018

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.

TomCJones commented Jan 13, 2018

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

This comment has been minimized.

Show comment
Hide comment
@Petermarcu
Member

Petermarcu commented Jan 13, 2018

@Eilon

This comment has been minimized.

Show comment
Hide comment
@Eilon

Eilon Jan 16, 2018

Member

@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.

Member

Eilon commented Jan 16, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@TomCJones

TomCJones Jan 16, 2018

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

TomCJones commented Jan 16, 2018

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

@bording

This comment has been minimized.

Show comment
Hide comment
@bording

bording Jan 16, 2018

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?

bording commented Jan 16, 2018

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

This comment has been minimized.

Show comment
Hide comment
@livarcocc

livarcocc Jan 16, 2018

Member

@mlorbetske to confirm the version that should be used!

Member

livarcocc commented Jan 16, 2018

@mlorbetske to confirm the version that should be used!

@mlorbetske

This comment has been minimized.

Show comment
Hide comment
@mlorbetske

mlorbetske Jan 16, 2018

Member

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.

Member

mlorbetske commented Jan 16, 2018

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

This comment has been minimized.

Show comment
Hide comment
@christiansk

christiansk Jan 21, 2018

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?

christiansk commented Jan 21, 2018

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

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Jan 21, 2018

Member

@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.

Member

Petermarcu commented Jan 21, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Jan 21, 2018

Member

@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.

Member

Petermarcu commented Jan 21, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@christiansk

christiansk Jan 21, 2018

@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?

christiansk commented Jan 21, 2018

@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

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Jan 22, 2018

Member

Here are a few things to note.

  1. 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. 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.

Member

Petermarcu commented Jan 22, 2018

Here are a few things to note.

  1. 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. 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

This comment has been minimized.

Show comment
Hide comment
@christiansk

christiansk Jan 22, 2018

Got it. Thanks!

christiansk commented Jan 22, 2018

Got it. Thanks!

@leecow

This comment has been minimized.

Show comment
Hide comment
@leecow

leecow Jan 22, 2018

Member

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

Member

leecow commented Jan 22, 2018

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

@cgountanis

This comment has been minimized.

Show comment
Hide comment
@cgountanis

cgountanis Mar 14, 2018

So 2.1.4 was removed and replaced with 2.1.101?

cgountanis commented Mar 14, 2018

So 2.1.4 was removed and replaced with 2.1.101?

@livarcocc

This comment has been minimized.

Show comment
Hide comment
@livarcocc

livarcocc Mar 14, 2018

Member

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.

Member

livarcocc commented Mar 14, 2018

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

This comment has been minimized.

Show comment
Hide comment
@cgountanis

cgountanis Mar 14, 2018

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

image

cgountanis commented Mar 14, 2018

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

image

@Petermarcu

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Mar 14, 2018

Member

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

Member

Petermarcu commented Mar 14, 2018

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

@DamianEdwards

This comment has been minimized.

Show comment
Hide comment
@DamianEdwards

DamianEdwards Mar 14, 2018

Contributor

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

Contributor

DamianEdwards commented Mar 14, 2018

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

This comment has been minimized.

Show comment
Hide comment
@cgountanis

cgountanis Mar 14, 2018

Dah, thank you. 🤯

cgountanis commented Mar 14, 2018

Dah, thank you. 🤯

@Petermarcu

This comment has been minimized.

Show comment
Hide comment
@Petermarcu

Petermarcu Mar 18, 2018

Member

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

Member

Petermarcu commented Mar 18, 2018

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

@Petermarcu Petermarcu closed this Mar 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment