Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit f440f4b

Browse filesBrowse files
Copilotgewarren
andcommitted
Remove misleading "always false" claim from Uri.UserEscaped documentation
Co-authored-by: gewarren <24882762+gewarren@users.noreply.github.com>
1 parent e585436 commit f440f4b
Copy full SHA for f440f4b

File tree

Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed

‎xml/System/Uri.xml

Copy file name to clipboardExpand all lines: xml/System/Uri.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6031,7 +6031,7 @@ The following examples show a URI and the results of calling <xref:System.Uri.Ge
60316031
60326032
## Remarks
60336033
6034-
The <xref:System.Uri> constructors that have a `dontEscape` parameter have been obsolete since .NET Framework 2.0 and shouldn't be used. As a result, this property is deprecated and shouldn't be used either.
6034+
The <xref:System.Uri.UserEscaped> property was originally designed to indicate that the string used to create the <xref:System.Uri> instance was completely escaped before it was passed to the constructor; that is, the `dontEscape` parameter of the constructor call was set to `true`. However, since the `dontEscape` parameter is now obsolete, this property is deprecated and shouldn't be used.
60356035
60366036
## Examples
60376037
The following example creates a <xref:System.Uri> instance and determines whether it was fully escaped when it was created.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.