Skip to content

Fix xref format issue in MetadataLoadContext and LinqDataSourceView #4266

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
May 21, 2020
Merged

Fix xref format issue in MetadataLoadContext and LinqDataSourceView #4266

Show file tree
Hide file tree
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.Reflection/MetadataLoadContext.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ If a core assembly cannot be found or if the core assembly is missing types, thi

* <xref:System.Reflection.MethodInfo.ReturnType?displayProperty=nameWithType>
* <xref:System.Reflection.MethodBase.GetParameters%2A?displayProperty=nameWithType>
* <xref:System.Type.BaseType?displayProperty-nameWithType>
* <xref:System.Type.BaseType?displayProperty=nameWithType>
* <xref:System.Type.GetInterfaces%2A?displayProperty=nameWithType>

* APIs that need to compare types to well-known core types will not throw an exception, and the comparison will evaluate to `false`. For example, if you do not specify a core assembly, <xref:System.Type.IsPrimitive> will return `false` for everything, even types named <xref:System.Int32>. Similarly, <xref:System.Type.GetTypeCode%2A?displayProperty=nameWithType> will return <xref:System.TypeCode.Object> for everything.
Expand Down
2 changes: 1 addition & 1 deletion xml/System.Web.UI.WebControls/LinqDataSourceView.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2104,7 +2104,7 @@ For more information, see the <xref:System.Web.UI.WebControls.LinqDataSource.Ord
## Remarks
The `SaveViewState` method is primarily used by control developers.

View state is the accumulation of the values of the properties for a server control. These values are automatically added to the <xref:System.Web.UI.Control.ViewState> property of the server control, which is an instance of the <xref>:System.Web.UI.StateBag> class. The <xref:System.Web.UI.Control.ViewState> value for the server control is then persisted to a string object after the save-state stage of the server control life cycle.
View state is the accumulation of the values of the properties for a server control. These values are automatically added to the <xref:System.Web.UI.Control.ViewState> property of the server control, which is an instance of the <xref:System.Web.UI.StateBag> class. The <xref:System.Web.UI.Control.ViewState> value for the server control is then persisted to a string object after the save-state stage of the server control life cycle.

When view state is saved, the string object that was persisted after the save-state stage of the server control life cycle is rendered to the browser as an HTML hidden element. When you create custom server controls, you can improve efficiency by overriding the `SaveViewState` method and modifying the `ViewState` property for your server control. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).

Expand Down