-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
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 Is this change intentional? In that case I probably should raise an issue in the VSTS Tasks GitHub instead |
Yes, same here. It break my VSTS build. An issue is submitted to VSTS task group. |
@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. |
@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? |
Created a new issue #1977 as the current one is an "announcement". |
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! |
Superseded by newer release 2.1.6 - see #2053 |
.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:
The text was updated successfully, but these errors were encountered: