Skip to content
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 October Update - 2.1.5 #1973

Closed
leecow opened this issue Oct 2, 2018 · 7 comments
Closed

.NET Core October Update - 2.1.5 #1973

leecow opened this issue Oct 2, 2018 · 7 comments

Comments

@leecow
Copy link
Member

leecow commented Oct 2, 2018

.NET Core October Update - 2.1.5

Release Notes
Download 2.1.5

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

@mkleijn
Copy link

mkleijn commented Oct 2, 2018

Hi, it seems the download urls in releases.json now uses absolute URL's instead of relative paths to the base url specified in blob-sdk
This breaks the .NET Core VSTS task from installing sdk 2.1.403 on my build agent

Is this change intentional? In that case I probably should raise an issue in the VSTS Tasks GitHub instead

@luchenatwork
Copy link

Yes, same here. It break my VSTS build. An issue is submitted to VSTS task group.
microsoft/azure-pipelines-tasks#8472

@leecow
Copy link
Member Author

leecow commented Oct 2, 2018

@mkleijn - yes, this is intentional. We have changed our publishing CDN and they do not have a stable "container" portion of the resulting URL. Without this, it would be extremely unpleasant to construct URLs in the current json file. Apologies for the breaking change.

@bishal-pdMSFT
Copy link

@leecow this is breaking the Azure pipelines(formerly VSTS) task. What is the long term approach here as want to make sure that the task work well over the time?
Are blob urls not longer going to be there? Will each location directly point to full dlc url? Are you going to change this behavior for older versions as well? There seems to be no set pattern.

@bishal-pdMSFT
Copy link

Created a new issue #1977 as the current one is an "announcement".

@asheeshv
Copy link

asheeshv commented Oct 3, 2018

I'm currently on .Net Core 2.0, and trying to upgrade to v2.1. I'm following this [https://docs.microsoft.com/en-us/aspnet/core/migration/20_21?view=aspnetcore-2.1](2.0 to 2.1). However, my .Net Core app uses the target framework as .Net4.7 using .Net core references to 2.0. With the 2.1.5 release, should I update these references to v2.1.5, or just update these to use 2.1. Would it be of any significant difference of going in with 2.1.0 over 2.1.5? Thanks!

@karelz
Copy link
Member

karelz commented Nov 13, 2018

Superseded by newer release 2.1.6 - see #2053

@karelz karelz closed this as completed Nov 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants