.NET 8: Host improvements

[richlander]

The following improvements should be considered for .NET 8.

• .NET 8: Tidy required .json assets for apps sdk#18597
• Improve UI of error dialog for missing framework/runtime #3816
• Use modern-themed buttons in the host error message box. #71288
• Localize apphost error page #71283
• .NET 8: Simplify RID Model #71285
• Improve host version selection semantics #71286
• Make call-to-action host errors source-build friendly #71287

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The following improvements should be considered for .NET 8.

• Improve UI of error dialog for missing framework/runtime #3816
• Localize apphost error page #71283
• Enable shared libraries and runtimes for a software suite #71282
• .NET 8: Tidy required .json assets for apps sdk#18597

Author:	richlander
Assignees:	-
Labels:	area-Host, untriaged
Milestone:	-

[NewUserHa]

original issue: #71993

I think since .NET Framework will not get newer versions and .NET 5+ is the successor, so Microsoft Windows should have a nice way to get the cool features from the newer version .NET.
an advantage of .NET is that it does need not users to download runtime, since it's supported by the OS. Therefore I think Microsoft Windows should keep supporting the .NET 5+ just like it supports the old .NET Framework.

BTW, the feature itself is not that important, but it can be a plus that makes .NET become more popular if windows can easily run .NET 5+ apps without installing something manually that other programming languages need.
So maybe still mark this feature as high priority?

I don't think every single .NET app have some built-in code to prompt this. since Windows still should be the main platform, it should support it as always. but for other platforms like *nix, BSD, a error window may be enough, just like other language runtimes.
But on Windows, .NET 5+ shouldn't be treat as a 3rd part software.

Because .NET 5+ cool features, c# can be more popular. Windows should keep continues compatible from the old .NET Framework to the new .NET 5+ in the easy usage for end-users aspects.

[richlander]

I responded at #71993 (comment)

[agocke]

Closing as we've made the changes we're planning for in .NET 8. Remaining work that we think is still valuable will move to .NET 9+