Skip to content

Removed mentions of Windows ME #2245

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
Apr 4, 2019
Merged

Removed mentions of Windows ME #2245

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
71 changes: 25 additions & 46 deletions xml/System.Windows.Forms/HtmlWindow.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,9 +68,7 @@
<format type="text/markdown"><![CDATA[

## Remarks
The <xref:System.Windows.Forms.MessageBox> class offers a more powerful version of the <xref:System.Windows.Forms.HtmlWindow.Alert%2A> method.

Although <xref:System.Windows.Forms.HtmlWindow.Alert%2A> accepts Unicode text as input, the Internet Explorer script prompt will not display non-Latin language text appropriately on Windows 95, Windows 98, Windows ME or Windows NT due to operating system limitations. For more information, see [INFO: Internet Explorer Script Prompts and MBCS/Unicode](https://support.microsoft.com/default.aspx?scid=kb;en-us;211147).
The <xref:System.Windows.Forms.MessageBox?displayProperty=nameWithType> class offers a more powerful version of the <xref:System.Windows.Forms.HtmlWindow.Alert%2A> method.

]]></format>
</remarks>
Expand Down Expand Up @@ -181,48 +179,31 @@
## Remarks
<xref:System.Windows.Forms.HtmlWindow.Confirm%2A> displays a modal dialog box; the user will not be able to access the underlying HTML page without first closing this dialog box.

Although <xref:System.Windows.Forms.HtmlWindow.Confirm%2A> accepts Unicode text as input, the Internet Explorer script prompt will not display non-Latin language text appropriately on Windows 95, Windows 98, Windows ME or Windows NT due to operating system limitations. For more information, see [INFO: Internet Explorer Script Prompts and MBCS/Unicode](https://support.microsoft.com/default.aspx?scid=kb;en-us;211147).



## Examples
Copy the following HTML and save it into a form called orderForm.htm:

`<HTML>`

`<BODY>`

`<FORM name="NewOrderForm">`

`Select Part Type:`

`<SELECT name="PartType">`

`<OPTION>AZ-3700`

`<OPTION>AZ-3701`

`<OPTION>AZ-3702`

`<SELECT><br>`

`Quantity: <INPUT type="text" name="PartQty" size="2" maxsize="2"><br>`

`Building/Desk:`

`<INPUT type="text" name="PartBuilding" size="2" maxsize="2"> /`

`<INPUT type="text" name="PartDesk" size="2" maxsize="2"><p>`

`<INPUT type="submit" value="Transmit Order">`

`</FORM>`

`</BODY>`

`</HTML>`

The following code example displays a <xref:System.Windows.Forms.HtmlWindow.Confirm%2A> dialog box when the user submits `NewOrderForm`.

Copy the following HTML and save it into a form called orderForm.htm:

```html
<HTML>
<BODY>
<FORM name="NewOrderForm">
Select Part Type:
<SELECT name="PartType">
<OPTION>AZ-3700
<OPTION>AZ-3701
<OPTION>AZ-3702
</SELECT><br/>
Quantity: <INPUT type="text" name="PartQty" size="2" maxsize="2" /><br/>
Building/Desk:
<INPUT type="text" name="PartBuilding" size="2" maxsize="2"/> /
<INPUT type="text" name="PartDesk" size="2" maxsize="2"/><p/>
<INPUT type="submit" value="Transmit Order"/>
</FORM>
</BODY>
</HTML>
```

The following example displays a <xref:System.Windows.Forms.HtmlWindow.Confirm%2A> dialog box when the user submits `NewOrderForm`.

[!code-csharp[System.Windows.Forms.HtmlWindow#10](~/samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.HtmlWindow/CS/Form1.cs#10)]
[!code-vb[System.Windows.Forms.HtmlWindow#10](~/samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.HtmlWindow/VB/Form1.vb#10)]
Expand Down Expand Up @@ -1338,8 +1319,6 @@
## Remarks
<xref:System.Windows.Forms.HtmlWindow.Prompt%2A> provides a quick, easy way to obtain simple text input from the user.

Although <xref:System.Windows.Forms.HtmlWindow.Prompt%2A> accepts Unicode text as input, the Internet Explorer script prompt will not display non-Latin language text appropriately on Windows 95, Windows 98, Windows ME or Windows NT due to operating system limitations. For more information, see [INFO: Internet Explorer Script Prompts and MBCS/Unicode](https://support.microsoft.com/default.aspx?scid=kb;en-us;211147).

]]></format>
</remarks>
<related type="ExternalDocumentation" href="https://msdn.microsoft.com/library/ms536673.aspx">prompt Method</related>
Expand Down
17 changes: 7 additions & 10 deletions xml/ns-System.Transactions.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,20 +6,17 @@

## Remarks

> [!IMPORTANT]
> You can only create applications using this namespace under the Windows 2000, Windows XP and Windows 2003 platforms. Creating a transaction under the Windows 98 and Windows ME platforms throws a <xref:System.PlatformNotSupportedException> .
The `System.Transactions` infrastructure makes transactional programming simple and efficient throughout the platform by supporting transactions initiated in SQL Server, ADO.NET, MSMQ, and the Microsoft Distributed Transaction Coordinator (MSDTC). It provides both an explicit programming model based on the <xref:System.Transactions.Transaction> class, as well as an implicit programming model using the <xref:System.Transactions.TransactionScope> class, in which transactions are automatically managed by the infrastructure. It is highly recommended that you use the easier implicit model for development. To get started, see the [Implementing An Implicit Transaction Using Transaction Scope](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/ms172152(v=vs.85)) topic. For more information on writing a transactional application, see [Writing A Transactional Application](~/docs/framework/data/transactions/writing-a-transactional-application.md).

The <xref:System.Transactions> infrastructure makes transactional programming simple and efficient throughout the platform by supporting transactions initiated in SQL Server, ADO.NET, MSMQ, and the Microsoft Distributed Transaction Coordinator (MSDTC). It provides both an explicit programming model based on the <xref:System.Transactions.Transaction> class, as well as an implicit programming model using the <xref:System.Transactions.TransactionScope> class, in which transactions are automatically managed by the infrastructure. It is highly recommended that you use the easier implicit model for development. To get started, see the [Implementing An Implicit Transaction Using Transaction Scope](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/ms172152(v=vs.85)) topic. For more information on writing a transactional application, see [Writing A Transactional Application](~/docs/framework/data/transactions/writing-a-transactional-application.md).
`System.Transactions` also provides types for you to implement a resource manager. The transaction manager native to the `System.Transactions` infrastructure allows volatile resources or a single durable resource enlistment to commit or roll back efficiently. For more information on implementing a resource manager, see [Implementing A Resource Manager](https://msdn.microsoft.com/library/81509719-d579-4530-831e-42e1acdef63e).

<xref:System.Transactions> also provides types for you to implement a resource manager. The transaction manager native to the <xref:System.Transactions> infrastructure allows volatile resources or a single durable resource enlistment to commit or roll back efficiently. For more information on implementing a resource manager, see [Implementing A Resource Manager](https://msdn.microsoft.com/library/81509719-d579-4530-831e-42e1acdef63e).
The transaction manager also transparently escalates local transactions to distributed transactions by coordinating through a disk-based transaction manager like the DTC, when an additional durable resource manager enlists itself with a transaction. There are two key ways that the `System.Transactions` infrastructure provides enhanced performance.

The transaction manager also transparently escalates local transactions to distributed transactions by coordinating through a disk-based transaction manager like the DTC, when an additional durable resource manager enlists itself with a transaction. There are two key ways that the <xref:System.Transactions> infrastructure provides enhanced performance.
- Dynamic Escalation, which means that the `System.Transactions` infrastructure only engages the MSDTC when it is actually required for a transaction. This area is covered in depth in the [Transaction Management Escalation](https://msdn.microsoft.com/library/5b87ae58-8ccf-4b9b-9715-41e4aade89b7) topic.

- Dynamic Escalation, which means that the <xref:System.Transactions> infrastructure only engages the MSDTC when it is actually required for a transaction. This area is covered in depth in the [Transaction Management Escalation](https://msdn.microsoft.com/library/5b87ae58-8ccf-4b9b-9715-41e4aade89b7) topic.
- Promotable Enlistments, which allows a resource, such as a database, to take ownership of the transaction if it is the only entity participating in the transaction. Later, if needed, the `System.Transactions` infrastructure can still escalate the management of the transaction to MSDTC. This further reduces the chance of using the MSDTC. This area is covered in depth in the [Optimization Using Single Phase Commit and Promotable Single Phase Notification](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/ms229980(v=vs.85)) topic.

- Promotable Enlistments, which allows a resource, such as a database, to take ownership of the transaction if it is the only entity participating in the transaction. Later, if needed, the <xref:System.Transactions> infrastructure can still escalate the management of the transaction to MSDTC. This further reduces the chance of using the MSDTC. This area is covered in depth in the [Optimization Using Single Phase Commit and Promotable Single Phase Notification](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/ms229980(v=vs.85)) topic.

<xref:System.Transactions> defines three levels of trust that restrict access on the types of resources it exposes. Specifically, the <xref:System.Transactions> assembly can be called by partially trusted code as it has been marked with the `AllowPartiallyTrustedCallers` attribute (APTCA). This attribute essentially removes the implicit <xref:System.Security.Permissions.SecurityAction.LinkDemand> for the `FullTrust` permission set that is otherwise automatically placed on each publicly accessible method in each type. However, some types and members still require stronger permissions.
`System.Transactions` defines three levels of trust that restrict access on the types of resources it exposes. Specifically, the *System.Transactions* assembly can be called by partially trusted code as it has been marked with the `AllowPartiallyTrustedCallers` attribute (APTCA). This attribute essentially removes the implicit <xref:System.Security.Permissions.SecurityAction.LinkDemand> for the `FullTrust` permission set that is otherwise automatically placed on each publicly accessible method in each type. However, some types and members still require stronger permissions.

The following is a list of types and members that are not callable by partially trusted code because they are decorated with the following declarative security attribute:

Expand Down Expand Up @@ -47,7 +44,7 @@

Core Development Technologies\Data Access\Transaction Processing\

For more information on how to use the <xref:System.Transactions> namespace, you can consult the conceptual documentation [Transaction Processing](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/w97s6fw4(v=vs.85)), located under the "Core Development Technologies\Data Access\Transaction Processing\\" section in the documentation. Specifically, you can find more information in the following topics.
For more information on how to use the `System.Transactions` namespace, you can consult the conceptual documentation [Transaction Processing](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/w97s6fw4(v=vs.85)), located under the "Core Development Technologies\Data Access\Transaction Processing\\" section in the documentation. Specifically, you can find more information in the following topics.

[Features Provided By System.Transactions](https://msdn.microsoft.com/library/99cc5ce0-b7fd-4d78-a553-a3dd3f17ed45)

Expand Down