core
core copied to clipboard
dotnet
releases-index.json: add .NET Framework (4.x)
URL(s)
https://github.com/dotnet/core/blob/main/release-notes/releases-index.json
Description
This is a list of .NET from 1.0 to 3.1 (skipping 4.x) and from 5.0 all the way to 9.0. Considering .NET Framework 4.x is built-in Windows, I don't see a reason why releases-index.json would not include this specific version, especially when it's still considered supported versions. I think .NET Framework should be included.
Does Json files have to be given permission or downloaded by the owner? Thx
On Sat, Jul 13, 2024 at 3:53 AM Obegg @.***> wrote:
URL(s)
https://github.com/dotnet/core/blob/main/release-notes/releases-index.json Description
This is a list of .NET from 1.0 to 3.1 (skipping 4.x) and from 5.0 all the way to 9.0. Considering .NET Framework 4.x is built-in Windows, I don't see a reason why releases-index.json https://github.com/dotnet/core/blob/main/release-notes/releases-index.json would not include this specific version, especially when it's still considered supported versions https://dotnet.microsoft.com/en-us/download/dotnet-framework. I think .NET Framework should be included.
— Reply to this email directly, view it on GitHub https://github.com/dotnet/core/issues/9408, or unsubscribe https://github.com/notifications/unsubscribe-auth/BA7FZAROCJABFPAK3HR5WJ3ZMEBLJAVCNFSM6AAAAABK2FSVJ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDMOBUGQ2TAMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
@billgothacked -- Check out:
https://github.com/dotnet/core/blob/main/release-notes/license-information.md
This repo is dedicated to .NET/.NET Core. We're not going to host .NET Framework content here.
We have (more limited) release notes for .NET Framework in another repo: https://github.com/microsoft/dotnet/tree/main/releases.
What would you do with such a file?
Do you download KBs for that? If you rely on Windows/Microsoft Update, you will get that automatically.
Do you download KBs for that? If you rely on Windows/Microsoft Update, you will get that automatically.
That's true, but it has it's limitations, for example: the .NET Framework after fresh install + Windows updates is 4.8, not 4.8.1.
OK. How would this file help with that?
If releases-index.json will be the same as .NET Core - It will be easier to keep .NET Framework up-to-date.
It has latest-release, latest-sdk and releases.json where you can get the latest .NET Framework download URL from.
How about this site?
https://dotnet.microsoft.com/download/dotnet-framework
I feel like there's a slight misunderstanding. I am familiar with the URL you mentioned, this is not what I propose. To be clear - A .json file (similar to the current one for .NET Core) would be perfect since it has the appropriate information such as which version the latest, sdk version, unsupported versions, URL to download each version and more. Simply adding .NET Framework to the current .json file would suffice if it's in the same format (same information as the rest of the entries). Hopefully this will clear the misunderstanding.
An example I created just for demonstration:
releases-index.json:
{
"$schema": "https://json.schemastore.org/dotnet-releases-index.json",
"releases-index": [
{
"channel-version": "4.0",
"latest-release": "4.8.1",
"latest-release-date": "2024-08-09",
"security": false,
"latest-runtime": "4.8.1",
"latest-sdk": "4.8.1",
"product": ".NET Framework",
"support-phase": "maintenance",
"eol-date": "",
"release-type": "sts",
"releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/4.0/releases.json",
"supported-os.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/4.0/supported-os.json"
}
]
}
releases.json:
{
"channel-version": "4.0",
"latest-release": "4.8.1",
"latest-release-date": "2024-08-09",
"latest-runtime": "4.8.1",
"latest-sdk": "4.8.1",
"support-phase": "active",
"release-type": "sts",
"eol-date": "",
"lifecycle-policy": "https://aka.ms/dotnetcoresupport",
"releases": [
{
"release-date": "2024-08-09",
"release-version": "4.8.1",
"security": true,
"cve-list": [
],
"release-notes": "https://github.com/microsoft/dotnet/blob/main/releases/net481/README.md",
"runtime": {
"version": "4.8.1",
"version-display": "4.8.1",
"vs-version": "17.8.12, 17.10.3",
"vs-mac-version": "",
"files": [
{
"name": "NDP481-Web.exe",
"rid": "dotnet-runtime-windows-sdk-x64",
"url": "https://go.microsoft.com/fwlink/?LinkId=2203304",
"hash": ""
}
]
},
"sdks": [
{
"version": "4.8.1",
"version-display": "4.8.1",
"runtime-version": "4.8.1",
"vs-version": "17.10.3",
"vs-mac-version": "",
"vs-support": "Visual Studio 2022 (v17.10)",
"vs-mac-support": "",
"csharp-version": "12.0",
"fsharp-version": "8.0",
"vb-version": "16.9",
"files": [
{
"name": "NDP481-DevPack-ENU.exe",
"rid": "dotnet-framework-windows-sdk-x64",
"url": "https://go.microsoft.com/fwlink/?linkid=2203306",
"hash": ""
}
]
}
]
}
I shared this issue with the folks on our team that manage .NET Framework.