Skip to content

Replace "tools" with "APIs" #3759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2020
Merged

Replace "tools" with "APIs" #3759

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@
<format type="text/markdown"><![CDATA[

## Remarks
For most scenarios that involve serializing to JSON and deserializing from JSON, we recommend the [tools in the System.Text.Json namespace](/dotnet/standard/serialization/system-text-json-overview).
For most scenarios that involve serializing to JSON and deserializing from JSON, we recommend the [APIs in the System.Text.Json namespace](/dotnet/standard/serialization/system-text-json-overview).

If your scenario requires the <xref:System.Runtime.Serialization.Json.DataContractJsonSerializer> class, you can use it to serialize instances of a type into a JSON document and to deserialize a JSON document into an instance of a type. For example, you can create a type named `Person` with properties that contain essential data, such as a name and address. You can then create and manipulate an instance of the `Person` class and write all of its property values in a JSON document for later retrieval. This JSON document can later be deserialized into the `Person` class or another class with an equivalent data contract.

Expand Down