Uri.EscapeUriString/EscapeDataString - stringToEscape limit 32766 was lifted in .NET 5+

[karelz]

How can we scope the limit to stringToEscape size to .NET Core 3.1 and earlier + .NET Framework?

The limitation was removed in 5.0 in PR dotnet/corefx#41686

[karelz]

cc @MihaZupan

[MihaZupan]

The length limit was lifted only on static (Un)Escape* methods, see dotnet/runtime#1857 (comment)

[karelz]

Updated title - we should update docs of the 2 methods:

• https://docs.microsoft.com/en-us/dotnet/api/system.uri.escapeuristring?view=netframework-4.8
• https://docs.microsoft.com/en-us/dotnet/api/system.uri.escapedatastring?view=netframework-4.8

[karelz]

@BillWagner who can help us provide guidance how to express the above limitation in the docs?
I am more than happy to make the change, I just don't know what is the right form of edits (dislaimer / inline version info / something else). Thanks!

[BillWagner]

I'll tag @joelmartinez

Is there a way to update this only in the .NET 5.0 monikers?

[joelmartinez]

Hi @BillWagner ... currently the only way to express this in the written documentation, is through prose ... which is to say something like, "in .NET 5, X limitation is lifted", or something in that way. There's not currently a way to scope summaries or remarks to a specific moniker :)

[karelz]

Thanks @joelmartinez ... what would be the preferred prose in this situation? (so that I can use it in other cases elsewhere)