Repo sync for protected CLA branch

docs/atl-mfc-shared/date-type.md

@@ -49,7 +49,7 @@ The following points should be noted when working with these date and time forma
 > [!CAUTION]
 > Note that because 6:00 AM is always represented by a fractional value 0.25 regardless of whether the integer representing the day is positive (after December 30, 1899) or negative (before December 30, 1899), a simple floating point comparison would erroneously sort any DATE representing 6:00 AM on a day earlier than 12/30/1899 as *later* than a DATE representing 7:00 AM on that same day.
 
-More information on issues related to the DATE and `COleDateTime` types can be found under [COleDateTime Class](../atl-mfc-shared/reference/coledatetime-class.md) and [Date and Time: Automation Support](../atl-mfc-shared/date-and-time-automation-support.md).
+More information on issues related to the DATE and `COleDateTime` types can be found under [COleDateTime Class](../atl-mfc-shared/reference/coledatetime-class.md) and [Date and Time: Automation Support](./date-and-time.md).
 
 ## See also
 

docs/atl-mfc-shared/reference/coledatetime-class.md

@@ -84,7 +84,7 @@ The `DATE` type is implemented as a floating-point value. Days are measured from
 > [!CAUTION]
 > In the table above, although day values become negative before midnight on December 30, 1899, time-of-day values do not. For example, 6:00 AM is always represented by a fractional value 0.25 regardless of whether the integer representing the day is positive (after December 30, 1899) or negative (before December 30, 1899). This means that a simple floating point comparison would erroneously sort a `COleDateTime` representing 6:00 AM on 12/29/1899 as **later** than one representing 7:00 AM on the same day.
 
-The `COleDateTime` class handles dates from January 1, 100, through December 31, 9999. The `COleDateTime` class uses the Gregorian calendar; it does not support Julian dates. `COleDateTime` ignores Daylight Saving Time. (See [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).)
+The `COleDateTime` class handles dates from January 1, 100, through December 31, 9999. The `COleDateTime` class uses the Gregorian calendar; it does not support Julian dates. `COleDateTime` ignores Daylight Saving Time. (See [Date and Time: Automation Support](../date-and-time.md).)
 
 > [!NOTE]
 > You can use the `%y` format to retrieve a two-digit year only for dates starting at 1900. If you use the `%y` format on a date before 1900, the code generates an ASSERT failure.
@@ -99,7 +99,7 @@ To avoid problems, specify a four-digit date. For example:
 
 Basic arithmetic operations for the `COleDateTime` values use the companion class [COleDateTimeSpan](../../atl-mfc-shared/reference/coledatetimespan-class.md). `COleDateTimeSpan` values define a time interval. The relationship between these classes is similar to the one between [CTime](../../atl-mfc-shared/reference/ctime-class.md) and [CTimeSpan](../../atl-mfc-shared/reference/ctimespan-class.md).
 
-For more information about the `COleDateTime` and `COleDateTimeSpan` classes, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the `COleDateTime` and `COleDateTimeSpan` classes, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## Requirements
 
@@ -231,7 +231,7 @@ For more information on the `time_t` data type, see the [time](../../c-runtime-l
 
 For more information, see the [SYSTEMTIME](/windows/win32/api/minwinbase/ns-minwinbase-systemtime) and [FILETIME](/windows/win32/api/minwinbase/ns-minwinbase-filetime) structures in the Windows SDK.
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 > [!NOTE]
 > The constructor using `DBTIMESTAMP` parameter is only available when OLEDB.h is included.
@@ -617,7 +617,7 @@ Valid return values range between 0 and 59.
 > [!NOTE]
 > The `COleDateTime` class does not support leap seconds.
 
-For more information about the implementation for `COleDateTime`, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the implementation for `COleDateTime`, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 For information on other member functions that query the value of this `COleDateTime` object, see the following member functions:
 
@@ -699,7 +699,7 @@ For more information about the operations that may set the status to invalid, se
 
 - [operator +=, -=](#operator_add_eq_-_eq)
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -737,7 +737,7 @@ For information on other member functions that query the value of this `COleDate
 
 - [GetDayOfYear](#getdayofyear)
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -756,7 +756,7 @@ DATE m_dt;
 > [!CAUTION]
 > Changing the value in the `DATE` object accessed by the pointer returned by this function will change the value of this `COleDateTime` object. It does not change the status of this `COleDateTime` object.
 
-For more information about the implementation of the `DATE` object, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the implementation of the `DATE` object, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="m_status"></a> COleDateTime::m_status
 
@@ -811,7 +811,7 @@ For more information on the `time_t` data type, see the [time](../../c-runtime-l
 
 For more information, see the [SYSTEMTIME](/windows/win32/api/minwinbase/ns-minwinbase-systemtime) and [FILETIME](/windows/win32/api/minwinbase/ns-minwinbase-filetime) structures in the Windows SDK.
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="operator_add_-"></a> COleDateTime::operator +, -
 
@@ -837,7 +837,7 @@ The **+** and **-** operators will assert if the `COleDateTime` object is set to
 
 For more information on the valid, invalid, and null status values, see the [m_status](#m_status) member variable.
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -864,7 +864,7 @@ For more information on the valid, invalid, and null status values, see the [m_s
 
 The **+=** and **-=** operators will assert if the `COleDateTime` object is set to null. See [COleDateTime Relational Operators](#coledatetime_relational_operators) for an example.
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="operator_date"></a> COleDateTime::operator DATE
 
@@ -876,7 +876,7 @@ operator DATE() const throw();
 
 ### Remarks
 
-This operator returns a `DATE` object whose value is copied from this `COleDateTime` object. For more information about the implementation of the `DATE` object, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+This operator returns a `DATE` object whose value is copied from this `COleDateTime` object. For more information about the implementation of the `DATE` object, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 The `DATE` operator will assert if the `COleDateTime` object is set to null. See [COleDateTime Relational Operators](#coledatetime_relational_operators) for an example.
 
@@ -939,7 +939,7 @@ In the case of VAR_DATEVALUEONLY, the time value is set to time 0, or midnight.
 
 If the string could not be converted to a date/time value or if there was a numerical overflow, the status of this `COleDateTime` object is invalid.
 
-For more information about the bounds and implementation for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds and implementation for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="setdate"></a> COleDateTime::SetDate
 
@@ -1012,7 +1012,7 @@ For information on member functions that query the value of this `COleDateTime`
 
 - [GetDayOfYear](#getdayofyear)
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -1096,7 +1096,7 @@ For information on member functions that query the value of this `COleDateTime`
 
 - [GetDayOfYear](#getdayofyear)
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -1189,7 +1189,7 @@ For information on member functions that query the value of this `COleDateTime`
 
 - [GetDayOfYear](#getdayofyear)
 
-For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTime` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 

docs/atl-mfc-shared/reference/coledatetimespan-class.md

@@ -65,7 +65,7 @@ A `COleDateTimeSpan` keeps time in days.
 
 `COleDateTimeSpan` is used with its companion class [COleDateTime](../../atl-mfc-shared/reference/coledatetime-class.md). `COleDateTime` encapsulates the `DATE` data type of OLE automation. `COleDateTime` represents absolute time values. All `COleDateTime` calculations involve `COleDateTimeSpan` values. The relation between these classes is analogous to the one between [CTime](../../atl-mfc-shared/reference/ctime-class.md) and [CTimeSpan](../../atl-mfc-shared/reference/ctimespan-class.md).
 
-For more information on the `COleDateTime` and `COleDateTimeSpan` classes, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information on the `COleDateTime` and `COleDateTimeSpan` classes, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## Requirements
 
@@ -134,7 +134,7 @@ All of these constructors create new `COleDateTimeSpan` objects initialized to t
 
 The status of the new `COleDateTimeSpan` object is set to valid.
 
-For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ### Example
 
@@ -375,7 +375,7 @@ The status of a `COleDateTimeSpan` object is invalid in the following cases:
 
 For more information about the operations that may set the status to invalid, see [COleDateTimeSpan::operator +, -](../../atl-mfc-shared/reference/coledatetime-class.md#operator_add_-) and [COleDateTimeSpan::operator +=, -=](../../atl-mfc-shared/reference/coledatetime-class.md#operator_add_eq_-_eq).
 
-For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="gettotaldays"></a> COleDateTimeSpan::GetTotalDays
 
@@ -575,7 +575,7 @@ For more information about the operations that may set the status to invalid, se
 > [!CAUTION]
 > This data member is for advanced programming situations. You should use the inline member functions [GetStatus](#getstatus) and [SetStatus](#setstatus). See `SetStatus` for further cautions regarding explicitly setting this data member.
 
-For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../../atl-mfc-shared/date-and-time-automation-support.md).
+For more information about the bounds for `COleDateTimeSpan` values, see the article [Date and Time: Automation Support](../date-and-time.md).
 
 ## <a name="operator_eq"></a> COleDateTimeSpan::operator =
 

docs/atl/active-template-library-atl-concepts.md

@@ -8,7 +8,7 @@ ms.assetid: a3960991-4d76-4da5-9568-3fa7fde53ff4
 
 The Active Template Library (ATL) is a set of template-based C++ classes that let you create small, fast Component Object Model (COM) objects. It has special support for key COM features, including stock implementations, dual interfaces, standard COM enumerator interfaces, connection points, tear-off interfaces, and ActiveX controls.
 
-If you do a lot of ATL programming, you will want to learn more about COM and .NET attributes, which is designed to simplify COM programming. For more information, see [Attributed Programming](../windows/attributed-programming-concepts.md). (COM and .NET attributes are not to be confused with the \[\[attribute]] feature in the C++ standard.)
+If you do a lot of ATL programming, you will want to learn more about COM and .NET attributes, which is designed to simplify COM programming. For more information, see [Attributed Programming](../windows/attributes/cpp-attributes-com-net.md). (COM and .NET attributes are not to be confused with the \[\[attribute]] feature in the C++ standard.)
 
 ## In This Section
 
@@ -89,7 +89,7 @@ Contains information on the ATL Project Wizard.
 [ATL Control Wizard](reference/atl-control-wizard.md)<br/>
 Discusses how to add classes.
 
-[Attributed Programming](../windows/attributed-programming-concepts.md)<br/>
+[Attributed Programming](../windows/attributes/cpp-attributes-com-net.md)<br/>
 Provides an overview on using attributes to simplify COM programming plus a list of links to more detailed topics.
 
 [ATL Class Overview](atl-class-overview.md)<br/>

docs/atl/example-implementing-a-property-page.md

@@ -126,7 +126,7 @@ When users want to apply their changes to the objects, the property page site wi
 
 To display this page, you need to create a simple helper object. The helper object will provide a method that simplifies the `OleCreatePropertyFrame` API for displaying a single page connected to a single object. This helper will be designed so that it can be used from Visual Basic.
 
-Use the [Add Class dialog box](../ide/add-class-dialog-box.md) and the [ATL Simple Object Wizard](../atl/reference/atl-simple-object-wizard.md) to generate a new class and use `Helper` as its short name. Once created, add a method as shown in the table below.
+Use the [Add Class dialog box](../ide/adding-a-class-visual-cpp.md#add-class-dialog-box) and the [ATL Simple Object Wizard](../atl/reference/atl-simple-object-wizard.md) to generate a new class and use `Helper` as its short name. Once created, add a method as shown in the table below.
 
 |Item|Value|
 |----------|-----------|

docs/atl/implementing-a-dialog-box.md

@@ -10,7 +10,7 @@ There are two ways to add a dialog box to your ATL project: use the ATL Dialog W
 
 ## Adding a Dialog Box with the ATL Dialog Wizard
 
-In the [Add Class dialog box](../ide/add-class-dialog-box.md), select the ATL Dialog object to add a dialog box to your ATL project. Fill in the ATL Dialog Wizard as appropriate and click **Finish**. The wizard adds a class derived from [CAxDialogImpl](../atl/reference/caxdialogimpl-class.md) to your project. Open **Resource View** from the **View** menu, locate your dialog, and double-click it to open it in the resource editor.
+In the [Add Class dialog box](../ide/adding-a-class-visual-cpp.md#add-class-dialog-box), select the ATL Dialog object to add a dialog box to your ATL project. Fill in the ATL Dialog Wizard as appropriate and click **Finish**. The wizard adds a class derived from [CAxDialogImpl](../atl/reference/caxdialogimpl-class.md) to your project. Open **Resource View** from the **View** menu, locate your dialog, and double-click it to open it in the resource editor.
 
 > [!NOTE]
 > If your dialog box is derived from `CAxDialogImpl`, it can host both ActiveX and Windows controls. If you don't want the overhead of ActiveX control support in your dialog box class, use [CSimpleDialog](../atl/reference/csimpledialog-class.md) or [CDialogImpl](../atl/reference/cdialogimpl-class.md) instead.

docs/atl/implementing-a-dual-interface.md

@@ -22,7 +22,7 @@ To use this class:
 
 ## ATL Simple Object Wizard
 
-If you want to create a new interface and a new class to implement it, you can use the [ATL Add Class dialog box](../ide/add-class-dialog-box.md), and then the [ATL Simple Object Wizard](../atl/reference/atl-simple-object-wizard.md).
+If you want to create a new interface and a new class to implement it, you can use the [ATL Add Class dialog box](../ide/adding-a-class-visual-cpp.md#add-class-dialog-box), and then the [ATL Simple Object Wizard](../atl/reference/atl-simple-object-wizard.md).
 
 ## Implement Interface Wizard
 

docs/atl/implementing-property-pages.md

@@ -14,13 +14,13 @@ The ATL Property Page wizard is not available in Visual Studio 2019 and later.
 
 ::: moniker range="<=vs-2017"
 
-Property pages are COM objects that implement the `IPropertyPage` or `IPropertyPage2` interface. ATL provides support for implementing property pages through the [ATL Property Page Wizard](../atl/reference/atl-property-page-wizard.md) in the [Add Class dialog box](../ide/add-class-dialog-box.md).
+Property pages are COM objects that implement the `IPropertyPage` or `IPropertyPage2` interface. ATL provides support for implementing property pages through the [ATL Property Page Wizard](../atl/reference/atl-property-page-wizard.md) in the [Add Class dialog box](../ide/adding-a-class-visual-cpp.md#add-class-dialog-box).
 
 To create a property page using ATL:
 
 - Create or open an ATL Dynamic-link library (DLL) server project.
 
-- Open the [Add Class dialog box](../ide/add-class-dialog-box.md) and select **ATL Property Page**.
+- Open the [Add Class dialog box](../ide/adding-a-class-visual-cpp.md#add-class-dialog-box) and select **ATL Property Page**.
 
 - Make sure your property page is apartment threaded (since it has a user interface).