MicrosoftDocs · gewarren · Feb 11, 2019 · Jan 28, 2019 · Jan 28, 2019 · Feb 8, 2019
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -6712,6 +6712,11 @@
             "redirect_url": "/visualstudio/mac/",
             "redirect_document_id": false
         },
+        {
+            "source_path": "mac/activation.md",
+            "redirect_url": "/visualstudio/mac/enable-subscription",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/cross-platform/overview-of-visual-studio-tools-for-unity.md",
             "redirect_url": "/visualstudio/cross-platform/visual-studio-tools-for-unity",

diff --git a/docs/debugger/c-cpp-assertions.md b/docs/debugger/c-cpp-assertions.md
diff --git a/docs/debugger/debug-interface-access/constants-debug-interface-access-sdk.md b/docs/debugger/debug-interface-access/constants-debug-interface-access-sdk.md
@@ -2,55 +2,55 @@
 title: "Constants (Debug Interface Access SDK) | Microsoft Docs"
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
-dev_langs: 
+dev_langs:
   - "C++"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "constants, DIA SDK"
   - "DIA SDK, constants"
 ms.assetid: aca4ec77-bc08-4cdd-a6ce-8d4a28ea5ea3
 author: "mikejo5000"
 ms.author: "mikejo"
 manager: jillfra
-ms.workload: 
+ms.workload:
   - "multiple"
 ---
 # Constants (Debug Interface Access SDK)
-These string constants can be used to identify various sections of a program debug database (PDB) file through the DIA SDK.  
-  
-## Constants  
- The following are declared as C/C++ macros.  
-  
-|Macro|Value|  
-|-----------|-----------|  
-|`DiaTable_Symbols`|L"Symbols"|  
-|`DiaTable_Sections`|L"Sections"|  
-|`DiaTable_SrcFiles`|L"SourceFiles"|  
-|`DiaTable_LineNums`|L"LineNumbers"|  
-|`DiaTable_SegMap`|L"SegmentMap"|  
-|`DiaTable_Dbg`|L"Dbg"|  
-|`DiaTable_InjSrc`|L"InjectedSource"|  
-|`DiaTable_FrameData`|L"FrameData"|  
-  
-## Example  
- Here is an example using one of these symbols:  
-  
-```C++  
-HRESULT GetSymbolTable(IDiaEnumTables *pEnumTables, IDiaTable **pTable)  
-{  
-    HRESULT hr;  
-    VARIANT var;  
-    var.vt      = VT_BSTR;  
-    var.bstrVal = SysAllocString( DiaTable_Symbols );  
-    hr = pEnumTables->Item( var, pTable );  
-    return(hr);  
-}  
-```  
-  
-## Requirements  
- Header: dia2.h  
-  
-## See Also  
- [Reference](../../debugger/debug-interface-access/debug-interface-access-sdk-reference.md)   
- [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)   
- [Interfaces (Debug Interface Access SDK)](../../debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md)   
- [IDiaEnumTables::Item](../../debugger/debug-interface-access/idiaenumtables-item.md)
+These string constants can be used to identify various sections of a program debug database (PDB) file through the DIA SDK.
+
+## Constants
+The following are declared as C/C++ macros.
+
+|Macro|Value|
+|-----------|-----------|
+|`DiaTable_Symbols`|L"Symbols"|
+|`DiaTable_Sections`|L"Sections"|
+|`DiaTable_SrcFiles`|L"SourceFiles"|
+|`DiaTable_LineNums`|L"LineNumbers"|
+|`DiaTable_SegMap`|L"SegmentMap"|
+|`DiaTable_Dbg`|L"Dbg"|
+|`DiaTable_InjSrc`|L"InjectedSource"|
+|`DiaTable_FrameData`|L"FrameData"|
+
+## Example
+Here is an example using one of these symbols:
+
+```C++
+HRESULT GetSymbolTable(IDiaEnumTables *pEnumTables, IDiaTable **pTable)
+{
+    HRESULT hr;
+    VARIANT var;
+    var.vt      = VT_BSTR;
+    var.bstrVal = SysAllocString( DiaTable_Symbols );
+    hr = pEnumTables->Item( var, pTable );
+    return(hr);
+}
+```
+
+## Requirements
+Header: dia2.h
+
+## See Also
+[Reference](../../debugger/debug-interface-access/debug-interface-access-sdk-reference.md)  
+[Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)  
+[Interfaces (Debug Interface Access SDK)](../../debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md)  
+[IDiaEnumTables::Item](../../debugger/debug-interface-access/idiaenumtables-item.md)
diff --git a/docs/debugger/debug-interface-access/idiadatasource-loadandvalidatedatafrompdb.md b/docs/debugger/debug-interface-access/idiadatasource-loadandvalidatedatafrompdb.md
@@ -2,87 +2,87 @@
 title: "IDiaDataSource::loadAndValidateDataFromPdb | Microsoft Docs"
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
-dev_langs: 
+dev_langs:
   - "C++"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "IDiaDataSource::loadAndValidateDataFromPdb method"
 ms.assetid: d66712dd-6c24-4192-919a-cce262066f0e
 author: "mikejo5000"
 ms.author: "mikejo"
 manager: jillfra
-ms.workload: 
+ms.workload:
   - "multiple"
 ---
 # IDiaDataSource::loadAndValidateDataFromPdb
-Opens and verifies that the program database (.pdb) file matches the signature information provided, and  prepares the .pdb file as a debug data source.  
-  
-## Syntax  
-  
-```C++  
-HRESULT loadAndValidateDataFromPdb (   
-   LPCOLESTR pdbPath,  
-   GUID*     pcsig70,  
-   DWORD     sig,  
-   DWORD     age  
-);  
-```  
-  
-#### Parameters  
- `pdbPath`  
- [in] The path to the .pdb file.  
-  
- `pcsig70`  
- [in] The GUID signature to verify against the .pdb file signature. Only .pdb files in [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] and later have GUID signatures.  
-  
- `sig`  
- [in] The 32-bit signature to verify against the .pdb file signature.  
-  
- `age`  
- [in] Age value to verify. The age does not necessarily correspond to any known time value, it is used to determine if a .pdb file is out of sync with a corresponding .exe file.  
-  
-## Return Value  
- If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.  
-  
-|Value|Description|  
-|-----------|-----------------|  
-|E_PDB_NOT_FOUND|Failed to open the file, or the file has an invalid format.|  
-|E_PDB_FORMAT|Attempted to access a file with an obsolete format.|  
-|E_PDB_INVALID_SIG|Signature does not match.|  
-|E_PDB_INVALID_AGE|Age does not match.|  
-|E_INVALIDARG|Invalid parameter.|  
-|E_UNEXPECTED|The data source has already been prepared.|  
-  
-## Remarks  
- A .pdb file contains both signature and age values. These values are replicated in the .exe or .dll file that matches the .pdb file. Before preparing the data source, this method verifies that the named .pdb file's signature and age match the values provided.  
-  
- To load a .pdb file without validation, use the [IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md) method.  
-  
- To gain access to the data load process (through a callback mechanism), use the [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md) method.  
-  
- To load a .pdb file directly from memory, use the [IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md) method.  
-  
-## Example  
-  
-```C++  
-IDiaDataSource* pSource;  // Previously created data source.  
-DEFINE_GUID(expectedGUIDSignature,0x1234,0x5678,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08);  
-DWORD expectedFileSignature = 0x12345678;  
-DWORD expectedAge           = 128;  
-  
-HRESULT hr;  
-hr = pSource->loadAndValidateDataFromPdb( L"yprog.pdb",  
-                                          &expectedGUIDSignature,  
-                                          expectedFileSignature,  
-                                          expectedAge);  
-if (FAILED(hr))  
-{  
-    // Report an error  
-}  
-  
-```  
-  
-## See Also  
- [IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)   
- [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md)   
- [IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md)   
- [IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md)
+Opens and verifies that the program database (.pdb) file matches the signature information provided, and  prepares the .pdb file as a debug data source.
+
+## Syntax
+
+```C++
+HRESULT loadAndValidateDataFromPdb ( 
+   LPCOLESTR pdbPath,
+   GUID*     pcsig70,
+   DWORD     sig,
+   DWORD     age
+);
+```
+
+#### Parameters
+`pdbPath`  
+[in] The path to the .pdb file.
+
+`pcsig70`  
+[in] The GUID signature to verify against the .pdb file signature. Only .pdb files in [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] and later have GUID signatures.
+
+`sig`  
+[in] The 32-bit signature to verify against the .pdb file signature.
+
+`age`  
+[in] Age value to verify. The age does not necessarily correspond to any known time value, it is used to determine if a .pdb file is out of sync with a corresponding .exe file.
+
+## Return Value
+If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.
+
+|Value|Description|
+|-----------|-----------------|
+|E_PDB_NOT_FOUND|Failed to open the file, or the file has an invalid format.|
+|E_PDB_FORMAT|Attempted to access a file with an obsolete format.|
+|E_PDB_INVALID_SIG|Signature does not match.|
+|E_PDB_INVALID_AGE|Age does not match.|
+|E_INVALIDARG|Invalid parameter.|
+|E_UNEXPECTED|The data source has already been prepared.|
+
+## Remarks
+A .pdb file contains both signature and age values. These values are replicated in the .exe or .dll file that matches the .pdb file. Before preparing the data source, this method verifies that the named .pdb file's signature and age match the values provided.
+
+To load a .pdb file without validation, use the [IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md) method.
+
+To gain access to the data load process (through a callback mechanism), use the [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md) method.
+
+To load a .pdb file directly from memory, use the [IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md) method.
+
+## Example
+
+```C++
+IDiaDataSource* pSource;  // Previously created data source.
+DEFINE_GUID(expectedGUIDSignature,0x1234,0x5678,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08);
+DWORD expectedFileSignature = 0x12345678;
+DWORD expectedAge           = 128;
+
+HRESULT hr;
+hr = pSource->loadAndValidateDataFromPdb( L"yprog.pdb",
+                                          &expectedGUIDSignature,
+                                          expectedFileSignature,
+                                          expectedAge);
+if (FAILED(hr))
+{
+    // Report an error
+}
+
+```
+
+## See Also
+[IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)  
+[IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md)  
+[IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md)  
+[IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md)