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

V4 feed is behind V3 feed for V3 runtime #297

Open
mattchenderson opened this issue Oct 15, 2021 · 2 comments
Open

V4 feed is behind V3 feed for V3 runtime #297

mattchenderson opened this issue Oct 15, 2021 · 2 comments

Comments

@mattchenderson
Copy link
Contributor

mattchenderson commented Oct 15, 2021

Per title, I noticed I was getting a really old Core Tools version (3.0.3442) in VS 16.11.5

Interestingly, @cachai2 is on 16.9.11 but is getting Core Tools 3.0.3785. These seem to be pulling from different feed versions. In both cases, they are looking for the GA V3 entry. But with different feed, wildly different results.

V4 feed

"v3": {
"release": "3.23.5",
"releaseQuality": "GA",
"hidden": false
},

"3.23.5": {
"templates": "https://functionscdn.azureedge.net/public/TemplatesApi/3.1.1648.zip",
"workerRuntimes": {
"dotnet": {
"netcore3": {
"displayInfo": {
"displayName": ".NET Core 3",
"hidden": false,
"displayVersion": "v3",
"targetFramework": ".NET Core",
"description": "LTS"
},
"capabilities": "",
"sdk": {
"name": "Microsoft.NET.Sdk.Functions",
"version": "3.0.13"
},
"default": true,
"localEntryPoint": "func.exe",
"targetFramework": "netcoreapp3.1",
"itemTemplates": "https://www.nuget.org/api/v2/package/Microsoft.Azure.WebJobs.ItemTemplates/3.1.1812",
"projectTemplates": "https://www.nuget.org/api/v2/package/Microsoft.Azure.WebJobs.ProjectTemplates/3.1.1812",
"projectTemplateId": {
"csharp": "Microsoft.AzureFunctions.ProjectTemplate.CSharp.3.x"
},
"localContainerBaseImage": "DOCKER|mcr.microsoft.com/azure-functions/dotnet:3.0-appservice",
"serviceAppSettings": {
"FUNCTIONS_EXTENSION_VERSION": "~3",
"FUNCTIONS_WORKER_RUNTIME": "dotnet"
},
"windowsSiteConfig": {
"netFrameworkVersion": "v4.0"
},
"linuxSiteConfig": {
"linuxFxVersion": "DOTNET|3.1"
}
},
"net5-isolated": {
"displayInfo": {
"displayName": ".NET 5",
"hidden": false,
"displayVersion": "v3",
"targetFramework": ".NET 5",
"description": "Isolated"
},
"capabilities": "isolated,net5",
"sdk": {
"name": "Microsoft.Azure.Functions.Worker.Sdk",
"version": "1.0.3"
},
"default": false,
"toolingSuffix": "net5-isolated",
"localEntryPoint": "dotnet.exe",
"targetFramework": "net5.0",
"itemTemplates": "https://www.nuget.org/api/v2/package/Microsoft.Azure.Functions.Worker.ItemTemplates/3.1.1796",
"projectTemplates": "https://www.nuget.org/api/v2/package/Microsoft.Azure.Functions.Worker.ProjectTemplates/3.1.1796",
"projectTemplateId": {
"csharp": "Microsoft.AzureFunctions.ProjectTemplate.CSharp.Isolated.3.x"
},
"localContainerBaseImage": "DOCKER|mcr.microsoft.com/azure-functions/dotnet-isolated:3.0-dotnet-isolated5.0-appservice",
"serviceAppSettings": {
"FUNCTIONS_EXTENSION_VERSION": "~3",
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated"
},
"windowsSiteConfig": {
"netFrameworkVersion": "v5.0"
},
"linuxSiteConfig": {
"linuxFxVersion": "DOTNET-ISOLATED|5.0"
}
}
}
},
"coreTools": [
{
"OS": "Linux",
"Architecture": "x64",
"downloadLink": "https://functionscdn.azureedge.net/public/3.0.3442/Azure.Functions.Cli.linux-x64.3.0.3442.zip",

V3 feed

"v3": {
"release": "3.30.0",
"displayName": "Azure Functions v3 (.NET Core)",
"displayVersion": "v3",
"releaseQuality": "GA",
"targetFramework": ".NET Core",
"hidden": false
}

"3.30.0": {
"Microsoft.NET.Sdk.Functions": "3.0.13",
"cli": "https://functionscdn.azureedge.net/public/3.0.3785/Azure.Functions.Cli.min.win-x86.3.0.3785.zip",

@fabiocav
Copy link
Member

Resolved by #301

The pipeline is also being updated by @soninaren to ensure this stays current.

The update will be reflected after a CDN refresh

@mattchenderson
Copy link
Contributor Author

mattchenderson commented Oct 21, 2021

Circling back here to provide an update: this worked.

I now see VS using release 3.28.0 - which is still behind, I think, but at least is relatively recent - and I'm seeing it running Core Tools version 3.0.3785.

Keeping the issue open for now for those pipeline changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants