Remove refs to Windows 9x (dotnet#5453)

Author: gewarren

xml/Microsoft.VisualBasic.ApplicationServices/AssemblyInfo.xml

@@ -800,10 +800,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Application.Info.WorkingSet` property has the same behavior as the <xref:System.Environment.WorkingSet%2A> property.  
-  
-> [!NOTE]
->  This property always returns zero for Windows 98 and Windows Millennium Edition.  
+ The `My.Application.Info.WorkingSet` property has the same behavior as the <xref:System.Environment.WorkingSet%2A> property.
   
 ## Availability by Project Type  
   
@@ -815,9 +812,7 @@
 |Windows Forms Control Library|**Yes**|  
 |Web Control Library|No|  
 |Windows Service|**Yes**|  
-|Web Site|No|  
-  
-   
+|Web Site|No| 
   
 ## Examples  
  This example uses the `My.Application.Info.WorkingSet` property to display the number of bytes of physical memory mapped to the application.  

xml/Microsoft.VisualBasic.ApplicationServices/User.xml

@@ -35,12 +35,7 @@
  For Windows applications, this property provides the same functionality as the <xref:System.Threading.Thread.CurrentPrincipal%2A> property. For Web applications, this property provides the same functionality as the <xref:System.Web.HttpContext.User%2A> property of the object returned by the <xref:System.Web.HttpContext.Current%2A> property.  
   
 > [!NOTE]
->  For Windows applications, only projects built on the **Windows Application** template initialize the `My.User` object by default. In all other Windows project types, you must initialize the `My.User` object by calling the <xref:Microsoft.VisualBasic.ApplicationServices.User.InitializeWithWindowsUser%2A> method explicitly or by assigning a value to <xref:System.Threading.Thread.CurrentPrincipal%2A>.  
-  
-> [!NOTE]
->  The `My.User` object cannot report information about the current Windows user when run under Windows 95 and Windows 98 because those operating systems do not support the concept of a logged-on user. You must implement custom authentication to use the `My.User` object on those operating systems.  
-  
-   
+>  For Windows applications, only projects built on the **Windows Application** template initialize the `My.User` object by default. In all other Windows project types, you must initialize the `My.User` object by calling the <xref:Microsoft.VisualBasic.ApplicationServices.User.InitializeWithWindowsUser%2A> method explicitly or by assigning a value to <xref:System.Threading.Thread.CurrentPrincipal%2A>.
   
 ## Examples  
  This example checks if the application is using Windows or custom authentication, and uses that information to parse the `My.User.Name` property.  
@@ -514,10 +509,7 @@
 ## Remarks  
  You can use the `My.User` object to get information about the current user.  
   
- The principal that authenticates the user also controls the format of the user name. By default, an application uses Windows authentication, and the user name has the format DOMAIN\USERNAME. A custom implementation of the principal does not necessarily use the same format.  
-  
-> [!NOTE]
->  The `My.User.Name` property returns an empty string when run under Windows 95 and Windows 98 because those operating systems do not recognize user names.  
+ The principal that authenticates the user also controls the format of the user name. By default, an application uses Windows authentication, and the user name has the format DOMAIN\USERNAME. A custom implementation of the principal does not necessarily use the same format.
   
 > [!NOTE]
 >  The exact behavior of the `My.User` object depends on the type of the application and on the operating system on which the application runs. For more information, see the <xref:Microsoft.VisualBasic.ApplicationServices.User> class overview.  

xml/Microsoft.VisualBasic.ApplicationServices/WebUser.xml

@@ -27,12 +27,7 @@
  For Windows applications, this property provides the same functionality as the <xref:System.Threading.Thread.CurrentPrincipal%2A> property. For Web applications, this property provides the same functionality as the <xref:System.Web.HttpContext.User%2A> property of the object returned by the <xref:System.Web.HttpContext.Current%2A> property.  
   
 > [!NOTE]
->  For Windows applications, only projects built on the **Windows Application** template initialize the `My.User` object by default. In all other Windows project types, you must initialize the `My.User` object by calling the <xref:Microsoft.VisualBasic.ApplicationServices.User.InitializeWithWindowsUser%2A> method explicitly or by assigning a value to <xref:System.Threading.Thread.CurrentPrincipal%2A>.  
-  
-> [!NOTE]
->  The `My.User` object cannot report information about the current Windows user when run under Windows 95 and Windows 98 because those operating systems do not support the concept of a logged-on user. You must implement custom authentication to use the `My.User` object on those operating systems.  
-  
-   
+>  For Windows applications, only projects built on the **Windows Application** template initialize the `My.User` object by default. In all other Windows project types, you must initialize the `My.User` object by calling the <xref:Microsoft.VisualBasic.ApplicationServices.User.InitializeWithWindowsUser%2A> method explicitly or by assigning a value to <xref:System.Threading.Thread.CurrentPrincipal%2A>.
   
 ## Examples  
  This example checks if the application is using Windows or custom authentication, and uses that information to parse the `My.User.Name` property.  

xml/Microsoft.VisualBasic.Devices/Ports.xml

@@ -574,10 +574,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Computer.Ports.SerialPortNames` property gets a collection of the names of the serial ports on the computer.  
-  
-> [!NOTE]
->  The port names returned by `My.Computer.Ports.SerialPortNames` may be incorrect when run on Windows 98. To prevent application errors, use exception handling, such as the `Try...Catch...Finally` statement or the `Using` statement, when using the port names to open ports.  
+ The `My.Computer.Ports.SerialPortNames` property gets a collection of the names of the serial ports on the computer.
   
  The following table lists an example of a task involving the `My.Computer.Ports.SerialPortNames` property.  
   

xml/Microsoft.VisualBasic.MyServices/RegistryProxy.xml

@@ -312,41 +312,7 @@
         <value>
           <see cref="T:Microsoft.Win32.RegistryKey" />
         </value>
-        <remarks>
-          <format type="text/markdown"><![CDATA[  
-  
-## Remarks  
- `HKEY_DYNDATA` is used to store dynamic registry data, such as that used by Virtual Device Drivers and is supported only on Windows 95/98 systems. On non-Windows 95/98 systems, calling any methods of the key returned by `Registry.DynData`, such as `CreateSubKey`, `DeleteSubKey`, `GetSubKeyCount`, `GetValueCount`, etc., will throw a <xref:System.IO.IOException>.  
-  
- The <xref:System.Security.Permissions.RegistryPermission> class, which is in the <xref:System.Security.Permissions> namespace, controls access to registry variables. Registry variables should not be stored in memory locations where code without <xref:System.Security.Permissions.RegistryPermission> can access them. Similarly, when granting permissions, grant the fewest privileges necessary to get the job done.  
-  
- Registry permission access values are defined by the <xref:System.Security.Permissions.RegistryPermissionAccess> enumeration. The following table details its members.  
-  
-|Value|Description|  
-|-----------|-----------------|  
-|AllAccess|Create, read, and write access to registry variables.|  
-|Create|Create access to registry variables.|  
-|NoAccess|No access to registry variables.|  
-|Read|Read access to registry variables.|  
-|Write|Write access to registry variables.|  
-  
- The following table lists examples of tasks involving the `My.Computer.Registry` object.  
-  
-|To|See|  
-|--------|---------|  
-|Create a registry key and set its value|[How to: Create a Registry Key and Set Its Value](/dotnet/visual-basic/developing-apps/programming/computer-resources/how-to-create-a-registry-key-and-set-its-value)|  
-|Delete a registry key|[How to: Delete a Registry Key](/dotnet/visual-basic/developing-apps/programming/computer-resources/how-to-delete-a-registry-key)|  
-|Read a value from a registry key|[How to: Read a Value from a Registry Key](/dotnet/visual-basic/developing-apps/programming/computer-resources/how-to-read-a-value-from-a-registry-key)|  
-  
-   
-  
-## Examples  
- This example deletes the subkey tree `Software\MyCompany\Preferences`.  
-  
- [!code-vb[VbVbalrMyRegistry#1](~/samples/snippets/visualbasic/VS_Snippets_VBCSharp/VbVbalrMyRegistry/VB/Class1.vb#1)]  
-  
- ]]></format>
-        </remarks>
+        <remarks>To be added.</remarks>
         <altmember cref="T:Microsoft.Win32.RegistryKey" />
         <altmember cref="F:Microsoft.Win32.Registry.DynData" />
         <related type="Article" href="/dotnet/visual-basic/language-reference/objects/">Objects (Visual Basic)</related>
@@ -528,9 +494,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `HKEY_PERFORMANCE_DATA` is used to access performance information for software components. Each software component creates keys for its objects and counters when it is installed and writes counter data while it is executing. This data is not stored in the registry, although the registry is used to access it. Instead, calling registry functions via `HKEY_PERFORMANCE_DATA` causes the system to collect the data from the appropriate system object managers.  
-  
- This key does not exist on Windows 98 systems; an attempt to use it other than calling the `Name` method will throw an <xref:System.IO.IOException>.  
+ `HKEY_PERFORMANCE_DATA` is used to access performance information for software components. Each software component creates keys for its objects and counters when it is installed and writes counter data while it is executing. This data is not stored in the registry, although the registry is used to access it. Instead, calling registry functions via `HKEY_PERFORMANCE_DATA` causes the system to collect the data from the appropriate system object managers.
   
  This key cannot normally be written to; attempting to create a subkey on it will throw an <xref:System.IO.IOException>.  
   

xml/Microsoft.VisualBasic/DateAndTime.xml

@@ -804,7 +804,7 @@ Dim LastMidnight As Date = CurrDatTim.Date   ' At midnight.
         <Parameter Name="Day" Type="System.Int32" />
       </Parameters>
       <Docs>
-        <param name="Year">Required. Integer expression from 1 through 9999. However, values below this range are also accepted. If <paramref name="Year" /> is 0 through 99, it is interpreted as being between 1930 and 2029, as explained in the "Remarks" section below. If <paramref name="Year" /> is less than 1, it is subtracted from the current year.</param>
+        <param name="Year">Required. Integer expression from 1 through 9999. However, values below this range are also accepted. If <paramref name="Year" /> is 0 through 99, it is interpreted as being between 1930 and 2029, as explained in the "Remarks" section. If <paramref name="Year" /> is less than 1, it is subtracted from the current year.</param>
         <param name="Month">Required. Integer expression from 1 through 12. However, values outside this range are also accepted. The value of <paramref name="Month" /> is offset by 1 and applied to January of the calculated year. In other words, (<paramref name="Month" /> - 1) is added to January. The year is recalculated if necessary. The following results illustrate this effect:  
 
  If <paramref name="Month" /> is 1, the result is January of the calculated year.  
@@ -823,15 +823,13 @@ Dim LastMidnight As Date = CurrDatTim.Date   ' At midnight.
  If <paramref name="Day" /> is -1, the result is the penultimate day of the previous month.  
 
  If <paramref name="Day" /> is past the end of the current month, the result is the appropriate day of the following month. For example, if <paramref name="Month" /> is 4 and <paramref name="Day" /> is 31, the result is May 1.</param>
-        <summary>Returns a <see langword="Date" /> value representing a specified year, month, and day, with the time information set to midnight (00:00:00).</summary>
-        <returns>A <see langword="Date" /> value representing a specified year, month, and day, with the time information set to midnight (00:00:00).</returns>
+        <summary>Returns a <see langword="Date" /> value representing the specified year, month, and day, with the time information set to midnight (00:00:00).</summary>
+        <returns>A value that represents the specified year, month, and day, with the time information set to midnight (00:00:00).</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Under Windows 98 or Windows 2000, two-digit years for the `Year` argument are interpreted based on user-defined computer settings. The default settings are that values from 0 through 29 are interpreted as the years 2000-2029, and values from 30 through 99 are interpreted as the years 1930-1999. For all other `Year` arguments, use a four-digit year; for example, 1924.  
-  
- Earlier versions of Windows interpret two-digit years based on the defaults described previously. To be sure the function returns the proper value, use a four-digit `Year`.  
+ Two-digit values for the `Year` argument are interpreted based on user-defined computer settings. The default settings are that values from 0 through 29 are interpreted as the years 2000-2029, and values from 30 through 99 are interpreted as the years 1930-1999. To signify all other years, use a four-digit year, for example, 1924.
   
  The following example demonstrates negative, zero, and positive argument values. Here, the `DateSerial` function returns a `Date` representing the day before the first day of March in the year 10 years before the current year; in other words, the last day of February ten years ago.  
   
@@ -847,9 +845,7 @@ Dim EndFeb As Date = DateSerial(-10, 3, 0)
   
 ```vb  
 Dim NewDateTime As Date = New Date(1978, 5, 6, 8, 29, 59, 900)  
-```  
-  
-   
+```
   
 ## Examples  
  This example uses the `DateSerial` function to return the date for the specified year, month, and day.  

xml/Microsoft.Win32/Registry.xml

@@ -288,29 +288,7 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
       </ReturnValue>
       <Docs>
         <summary>Contains dynamic registry data. This field reads the Windows registry base key HKEY_DYN_DATA.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[
-
-## Remarks
- The Windows 98/Windows Me registry supports both static data (which is stored on disk in the registry) and dynamic data (which changes frequently, such as performance statistics). This dynamic data area is the mechanism that allows Virtual Device Drivers (VxDs) to provide real-time data to Win32 applications that can run remotely as well as locally. It also allows the system monitor to provide performance statistics on remote Windows 98/Windows Me systems.
-
- VxDs are not limited to performance data. They can provide any data they want to pass from Ring 0 to Ring 3 efficiently without monopolizing the CPU. The registry supports dynamic data by storing a pointer to a function that returns a value (or many values). When a Registry call queries values associated with a dynamic key, that function is called to return the desired value or values.
-
-> [!NOTE]
->  Dynamic keys were introduced in Microsoft Windows 95 to handle dynamic Registry data. They are supported only in Windows 98/Windows Me.
-
-
-
-## Examples
- The following example demonstrates how to retrieve the subkeys of this key, and prints their names to the screen. Use the <xref:Microsoft.Win32.RegistryKey.OpenSubKey%2A> method to create an instance of the particular subkey of interest. You can then use other operations in <xref:Microsoft.Win32.RegistryKey> to manipulate that key. Note that this example can return no results, since there might not be dynamic data available, or you might not be running Windows 98/ME. Using this key may cause an error on other systems.
-
- [!code-cpp[Classic Registry.DynData Example#1](~/samples/snippets/cpp/VS_Snippets_CLR_Classic/classic Registry.DynData Example/CPP/source.cpp#1)]
- [!code-csharp[Classic Registry.DynData Example#1](~/samples/snippets/csharp/VS_Snippets_CLR_Classic/classic Registry.DynData Example/CS/source.cs#1)]
- [!code-vb[Classic Registry.DynData Example#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_Classic/classic Registry.DynData Example/VB/source.vb#1)]
-
- ]]></format>
-        </remarks>
-        <exception cref="T:System.ObjectDisposedException">The operating system does not support dynamic data; that is, it is not Windows 98, Windows 98 Second Edition, or Windows Millennium Edition (Windows Me).</exception>
+        <remarks>To be added.</remarks>
       </Docs>
     </Member>
     <Member MemberName="GetValue">
@@ -611,11 +589,6 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
 
  This overload is equivalent to calling the <xref:Microsoft.Win32.Registry.SetValue%28System.String%2CSystem.String%2CSystem.Object%2CMicrosoft.Win32.RegistryValueKind%29> method overload with <xref:Microsoft.Win32.RegistryValueKind.Unknown?displayProperty=nameWithType>.
 
-> [!NOTE]
->  On Windows 98 and Windows Millennium Edition (Windows Me), the registry is not Unicode, and not all Unicode characters are valid for all code pages. A Unicode character that is invalid for the current code page is replaced by the best available match. No exception is thrown.
-
-
-
 ## Examples
  The following code example stores values of several data types in an example key, creating the key as it does so, and then retrieves and displays the values. The example demonstrates storing and retrieving the default (nameless) name/value pair, and the use of `defaultValue` when a name/value pair does not exist.
 
@@ -708,11 +681,6 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
 > [!NOTE]
 >  If boxed values are passed for <xref:Microsoft.Win32.RegistryValueKind.DWord?displayProperty=nameWithType> or <xref:Microsoft.Win32.RegistryValueKind.QWord?displayProperty=nameWithType>, the conversion is done using the invariant culture.
 
-> [!NOTE]
->  On Windows 98 and Windows Millennium Edition (Windows Me), the registry is not Unicode, and not all Unicode characters are valid for all code pages. A Unicode character that is invalid for the current code page is replaced by the best available match. No exception is thrown.
-
-
-
 ## Examples
  The following code example stores values of several data types in an example key, creating the key as it does so, and then retrieves and displays the values. The example demonstrates storing and retrieving the default (nameless) name/value pair, and the use of `defaultValue` when a name/value pair does not exist.
 
@@ -772,9 +740,7 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This key contains a branch for each user of the computer. The default configuration is supplied for new users on the local computer and for the default current user if the user has not changed preferences. Because Windows 98/ME also supports Registry.Users, applications can access the user-specific information the same way they do under Windows 2000. Each user's information is stored in a separate file, which can be stored locally or on a network server. Windows 98/ME can copy this file to the user's current system so that settings can move from one computer to another with the user.
-
-
+ This key contains a branch for each user of the computer. The default configuration is supplied for new users on the local computer and for the default current user if the user has not changed preferences.
 
 ## Examples
  The following example demonstrates how to retrieve the subkeys of this key, and prints their names to the screen. Use the <xref:Microsoft.Win32.RegistryKey.OpenSubKey%2A> method to create an instance of the particular subkey of interest. You can then use other operations in <xref:Microsoft.Win32.RegistryKey> to manipulate that key.