[NETE2ESDK][Loc]The hyperlink for contents on NET 7.0.0 windows server hosting installer UI on loc OS is EN not loc link.

[vdanche]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The hyperlink for contents on windows hosting bundle installer UI on loc OS is EN link not loc link.

Expected Behavior

The link should be loc link.

Steps To Reproduce

Double-click on NET7.0.0 dotne-hosting installer .exe on Loc OS e.g Russian OS.
On installation UI, Click the link for "here" "license term" "privacy statement"

Actual Result:
e.g RU:

here: https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-6.0
license term : https://dotnet.microsoft.com/en-us/dotnet_library_license.htm
privacy statement: https://privacy.microsoft.com/en-us/privacystatement/

EN:

here: https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-6.0
license term : https://dotnet.microsoft.com/en-us/dotnet_library_license.htm
privacy statement: https://privacy.microsoft.com/en-us/privacystatement/

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[dougbu]

Is this a regression from 6.0.x? I doubt it because the relevant code hasn't changed in a while.

That said, the use of ...?view=aspnetcore-6.0 could be considered a regression from 6.0.x because the same link would have been perfect then.

[dougbu]

@cristianosuzuki77 is there a way to have the correct locale identifiers substituted for en-us during the loc process for WXL files❔

[mkArtakMSFT]

Ping @cristianosuzuki77

[dougbu]

Will see if we can use language-neutral links for these parts of the UI. Will require more work in main because I need to add loc comments there. So, I'll do a manual release/7.0 change and double check release/6.0 as well (because that's LTS).

[dougbu]

Oh, I think I see…

@mkArtakMSFT I don't know how to validate fwlinks (I of course land on en-us pages) and would appreciate you checking the following

• https://go.microsoft.com/fwlink/?LinkId=329770 should forward to https://dotnet.microsoft.com/dotnet_library_license.htm
• https://go.microsoft.com/fwlink/?LinkId=786378 should forward to https://privacy.microsoft.com/privacystatement/
• https://go.microsoft.com/fwlink/?LinkId=798277 should forward to https://learn.microsoft.com/aspnet/core/host-and-deploy/iis/?view=aspnetcore-7.0

That is, none of the above should forward to a local-specific URI e.g., https://dotnet.microsoft.com/en-us/dotnet_library_license.htm

[mkArtakMSFT]

Ok, the first link is owned by @terrajobst, the second one is owned by @ChrisSfanos and the third one is owned by @danroth27.

@dougbu how safe is it to simply change those links? Maybe they're used somewhere else? Can we instead create new aka.ms links to the targets that you need them to point to?

[dougbu]

@dougbu how safe is it to simply change those links? Maybe they're used somewhere else? Can we instead create new aka.ms links to the targets that you need them to point to?

I don't know about whether these fwlinks can be changed nor other uses but hope the owners do. aka.ms links would be fine if we can't change them.

To cover 6.0.x (...?view=aspnetcore-6.0) for #44615 as well, would actually need 4 distinct locale-independent links of either type.