more msdn link conversions

Author: mikeblome

docs/atl/reference/ccommodule-class.md

@@ -350,7 +350,7 @@ HRESULT RegisterClassObjects(DWORD dwClsContext, DWORD dwFlags) throw();
 ### Parameters
 
 *dwClsContext*<br/>
-[in] Specifies the context in which the class object is to be run. Possible values are CLSCTX_INPROC_SERVER, CLSCTX_INPROC_HANDLER, or CLSCTX_LOCAL_SERVER. For a description of these values, see [CLSCTX](https://msdn.microsoft.com/library/windows/desktop/ms693716) in the Windows SDK.
+[in] Specifies the context in which the class object is to be run. Possible values are CLSCTX_INPROC_SERVER, CLSCTX_INPROC_HANDLER, or CLSCTX_LOCAL_SERVER. For a description of these values, see [CLSCTX](/windows/desktop/api/wtypesbase/ne-wtypesbase-tagclsctx) in the Windows SDK.
 
 *dwFlags*<br/>
 [in] Determines the connection types to the class object. Possible values are REGCLS_SINGLEUSE, REGCLS_MULTIPLEUSE, or REGCLS_MULTI_SEPARATE. For a description of these values, see [REGCLS](/windows/desktop/api/combaseapi/ne-combaseapi-tagregcls) in the Windows SDK.

docs/atl/reference/composite-control-global-functions.md

@@ -58,7 +58,7 @@ ATLAPI_(int) AtlAxDialogBox(
 [in] Identifies an instance of the module whose executable file contains the dialog box template.
 
 *lpTemplateName*<br/>
-[in] Identifies the dialog box template. This parameter is either the pointer to a null-terminated character string that specifies the name of the dialog box template or an integer value that specifies the resource identifier of the dialog box template. If the parameter specifies a resource identifier, its high-order word must be zero and its low-order word must contain the identifier. You can use the [MAKEINTRESOURCE](https://msdn.microsoft.com/library/windows/desktop/ms648029) macro to create this value.
+[in] Identifies the dialog box template. This parameter is either the pointer to a null-terminated character string that specifies the name of the dialog box template or an integer value that specifies the resource identifier of the dialog box template. If the parameter specifies a resource identifier, its high-order word must be zero and its low-order word must contain the identifier. You can use the [MAKEINTRESOURCE](/windows/desktop/api/winuser/nf-winuser-makeintresourcea) macro to create this value.
 
 *hWndParent*<br/>
 [in] Identifies the window that owns the dialog box.
@@ -105,7 +105,7 @@ ATLAPI_(HWND) AtlAxCreateDialog(
 [in] Identifies an instance of the module whose executable file contains the dialog box template.
 
 *lpTemplateName*<br/>
-[in] Identifies the dialog box template. This parameter is either the pointer to a null-terminated character string that specifies the name of the dialog box template or an integer value that specifies the resource identifier of the dialog box template. If the parameter specifies a resource identifier, its high-order word must be zero and its low-order word must contain the identifier. You can use the [MAKEINTRESOURCE](https://msdn.microsoft.com/library/windows/desktop/ms648029) macro to create this value.
+[in] Identifies the dialog box template. This parameter is either the pointer to a null-terminated character string that specifies the name of the dialog box template or an integer value that specifies the resource identifier of the dialog box template. If the parameter specifies a resource identifier, its high-order word must be zero and its low-order word must contain the identifier. You can use the [MAKEINTRESOURCE](/windows/desktop/api/winuser/nf-winuser-makeintresourcea) macro to create this value.
 
 *hWndParent*<br/>
 [in] Identifies the window that owns the dialog box.

docs/atl/reference/server-registration-global-functions.md

@@ -111,7 +111,7 @@ ATLINLINE ATLAPI AtlComModuleRegisterClassObjects(
 Pointer to the COM module.
 
 *dwClsContext*<br/>
-Specifies the context in which the class object is to be run. Possible values are CLSCTX_INPROC_SERVER, CLSCTX_INPROC_HANDLER, or CLSCTX_LOCAL_SERVER. See [CLSCTX](https://msdn.microsoft.com/library/windows/desktop/ms693716) for more details.
+Specifies the context in which the class object is to be run. Possible values are CLSCTX_INPROC_SERVER, CLSCTX_INPROC_HANDLER, or CLSCTX_LOCAL_SERVER. See [CLSCTX](/windows/desktop/api/wtypesbase/ne-wtypesbase-tagclsctx) for more details.
 
 *dwFlags*<br/>
 Determines the connection types to the class object. Possible values are REGCLS_SINGLEUSE, REGCLS_MULTIPLEUSE, or REGCLS_MULTI_SEPARATE. See [REGCLS](/windows/desktop/api/combaseapi/ne-combaseapi-tagregcls) for more details.

docs/build/building-c-cpp-side-by-side-assemblies.md

@@ -20,7 +20,7 @@ A Visual C++ application may use one or several DLLs in different parts of the a
 By default, when a DLL is built with Visual Studio, it has an [application manifest](/windows/desktop/SbsCs/application-manifests) embedded as an RT_MANIFEST resource with ID equal to 2. Just as for an executable, this manifest describes dependencies of this DLL on other assemblies. This assumes that the DLL is not part of a side-by-side assembly and applications that depend on this DLL are not going to use an application manifest to load it, but instead rely on the operating system loader to find this DLL on the system path.
 
 > [!NOTE]
-> It is important for a DLL that uses an application manifest to have the manifest embedded as a resource with ID equal to 2. If the DLL is dynamically loaded at runtime (for example, using the [LoadLibrary](https://msdn.microsoft.com/library/windows/desktop/ms684175) function), the operating system loader loads dependent assemblies specified in the DLL's manifest. An external application manifest for DLLs is not checked during a `LoadLibrary` call. If the manifest is not embedded, the loader may attempt to load incorrect versions of assemblies or fail to find to find dependent assemblies.
+> It is important for a DLL that uses an application manifest to have the manifest embedded as a resource with ID equal to 2. If the DLL is dynamically loaded at runtime (for example, using the [LoadLibrary](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibrarya) function), the operating system loader loads dependent assemblies specified in the DLL's manifest. An external application manifest for DLLs is not checked during a `LoadLibrary` call. If the manifest is not embedded, the loader may attempt to load incorrect versions of assemblies or fail to find to find dependent assemblies.
 
 One or several related DLLs can be repackaged into a side-by-side assembly with a corresponding [assembly manifest](/windows/desktop/SbsCs/assembly-manifests), which describes which files form the assembly as well as the dependence of the assembly on other side-by-side assemblies.
 

docs/build/freelibrary-and-afxfreelibrary.md

@@ -14,7 +14,7 @@ ms.workload: ["cplusplus"]
 ---
 # FreeLibrary and AfxFreeLibrary
 
-Processes that explicitly link to a DLL call the [FreeLibrary](https://msdn.microsoft.com/library/windows/desktop/ms683152(v=vs.85).aspx) function when the DLL module is no longer needed. This function decrements the module's reference count and, if the reference count is zero, unmaps it from the address space of the process.
+Processes that explicitly link to a DLL call the [FreeLibrary](/windows/desktop/api/libloaderapi/nf-libloaderapi-freelibrary).aspx) function when the DLL module is no longer needed. This function decrements the module's reference count and, if the reference count is zero, unmaps it from the address space of the process.
 
 In an MFC application, use [AfxFreeLibrary](../mfc/reference/application-information-and-management.md#afxfreelibrary) instead of `FreeLibrary` to unload an MFC extension DLL. The interface (function prototype) for `AfxFreeLibrary` is the same as `FreeLibrary`.
 
@@ -33,5 +33,5 @@ In an MFC application, use [AfxFreeLibrary](../mfc/reference/application-informa
 ## See Also
 
 [DLLs in Visual C++](../build/dlls-in-visual-cpp.md)<br/>
-[FreeLibrary](https://msdn.microsoft.com/library/windows/desktop/ms683152(v=vs.85).aspx)
+[FreeLibrary](/windows/desktop/api/libloaderapi/nf-libloaderapi-freelibrary).aspx)
 [AfxFreeLibrary](../mfc/reference/application-information-and-management.md#afxfreelibrary)

docs/build/getprocaddress.md

@@ -14,7 +14,7 @@ ms.workload: ["cplusplus"]
 ---
 # GetProcAddress
 
-Processes explicitly linking to a DLL call [GetProcAddress](https://msdn.microsoft.com/library/windows/desktop/ms683212) to obtain the address of an exported function in the DLL. You use the returned function pointer to call the DLL function. **GetProcAddress** takes as parameters the DLL module handle (returned by either **LoadLibrary**, `AfxLoadLibrary`, or **GetModuleHandle**) and takes either the name of the function you want to call or the function's export ordinal.
+Processes explicitly linking to a DLL call [GetProcAddress](/windows/desktop/api/libloaderapi/nf-libloaderapi-getprocaddress) to obtain the address of an exported function in the DLL. You use the returned function pointer to call the DLL function. **GetProcAddress** takes as parameters the DLL module handle (returned by either **LoadLibrary**, `AfxLoadLibrary`, or **GetModuleHandle**) and takes either the name of the function you want to call or the function's export ordinal.
 
 Because you are calling the DLL function through a pointer and there is no compile-time type checking, make sure that the parameters to the function are correct so that you do not overstep the memory allocated on the stack and cause an access violation. One way to help provide type-safety is to look at the function prototypes of the exported functions and create matching typedefs for the function pointers. For example:
 
@@ -60,7 +60,7 @@ You can only obtain the export ordinal if the DLL you are linking to is built wi
 
 - [LoadLibrary and AfxLoadLibrary](../build/loadlibrary-and-afxloadlibrary.md)
 
-- [FreeLibrary](https://msdn.microsoft.com/library/windows/desktop/ms683152)
+- [FreeLibrary](/windows/desktop/api/libloaderapi/nf-libloaderapi-freelibrary)
 
 - [Exporting from a DLL Using DEF Files](../build/exporting-from-a-dll-using-def-files.md)
 

docs/build/reference/constraints-of-delay-loading-dlls.md

@@ -32,9 +32,9 @@ There are constraints regarding the delay loading of imports.
 ## See Also
 
 [Linker Support for Delay-Loaded DLLs](../../build/reference/linker-support-for-delay-loaded-dlls.md)<br/>
-[LoadLibrary function](https://msdn.microsoft.com/library/windows/desktop/ms684175.aspx)<br/>
-[GetModuleHandle function](https://msdn.microsoft.com/library/windows/desktop/ms683199.aspx)<br/>
-[GetProcAddress function](https://msdn.microsoft.com/library/windows/desktop/ms683212.aspx)<br/>
+[LoadLibrary function](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibrarya)<br/>
+[GetModuleHandle function](/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulehandlea)<br/>
+[GetProcAddress function](/windows/desktop/api/libloaderapi/nf-libloaderapi-getprocaddress)<br/>
 [TlsAlloc function](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-tlsalloc)<br/>
 [TlsFree function](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-tlsfree)<br/>
 [TlsGetValue function](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-tlsgetvalue)<br/>

docs/build/reference/delay-delay-load-import-settings.md

@@ -29,7 +29,7 @@ The /DELAY option controls [delayed loading](../../build/reference/linker-suppor
 
 - The NOBIND qualifier tells the linker not to include a bindable IAT in the final image. The default is to create the bindable IAT for delay-loaded DLLs. The resulting image cannot be statically bound. (Images with bindable IATs may be statically bound prior to execution.) See [/BIND](../../build/reference/bind.md).
 
-   If the DLL is bound, the helper function will attempt to use the bound information instead of calling [GetProcAddress](https://msdn.microsoft.com/library/windows/desktop/ms683212.aspx) on each of the referenced imports. If either the timestamp or the preferred address does not match those of the loaded DLL, the helper function will assume the bound IAT is out of date and will proceed as if the bound IAT does not exist.
+   If the DLL is bound, the helper function will attempt to use the bound information instead of calling [GetProcAddress](/windows/desktop/api/libloaderapi/nf-libloaderapi-getprocaddress) on each of the referenced imports. If either the timestamp or the preferred address does not match those of the loaded DLL, the helper function will assume the bound IAT is out of date and will proceed as if the bound IAT does not exist.
 
    NOBIND causes your program image to be larger but can speed load time of the DLL. If you never intend to bind the DLL, NOBIND will prevent the bound IAT from being generated.
 

docs/build/reference/exports.md

@@ -56,7 +56,7 @@ To find the decorated names produced by the compiler, use the [DUMPBIN](../../bu
 
 You can use \@*ordinal* to specify that a number, and not the function name, goes into the DLL's export table. Many Windows DLLs export ordinals to support legacy code. It was common to use ordinals in 16-bit Windows code, because it can help minimize the size of a DLL. We don’t recommend exporting functions by ordinal unless your DLL’s clients need it for legacy support. Because the .LIB file will contain the mapping between the ordinal and the function, you can use the function name as you normally would in projects that use the DLL.
 
-By using the optional **NONAME** keyword, you can export by ordinal only and reduce the size of the export table in the resulting DLL. However, if you want to use [GetProcAddress](https://msdn.microsoft.com/library/windows/desktop/ms683212.aspx) on the DLL, you must know the ordinal because the name will not be valid.
+By using the optional **NONAME** keyword, you can export by ordinal only and reduce the size of the export table in the resulting DLL. However, if you want to use [GetProcAddress](/windows/desktop/api/libloaderapi/nf-libloaderapi-getprocaddress) on the DLL, you must know the ordinal because the name will not be valid.
 
 The optional keyword **PRIVATE** prevents *entryname* from being included in the import library generated by LINK. It does not affect the export in the image also generated by LINK.
 

docs/c-language/argument-description.md

@@ -19,7 +19,7 @@ The `argc` parameter in the **main** and **wmain** functions is an integer speci
 
 The `argv` parameter is an array of pointers to null-terminated strings representing the program arguments. Each element of the array points to a string representation of an argument passed to **main** (or **wmain**). (For information about arrays, see [Array Declarations](../c-language/array-declarations.md).) The `argv` parameter can be declared either as an array of pointers to type `char` (`char *argv[]`) or as a pointer to pointers to type `char` (`char **argv`). For **wmain**, the `argv` parameter can be declared either as an array of pointers to type `wchar_t` (`wchar_t *argv[]`) or as a pointer to pointers to type `wchar_t` (`wchar_t **argv`).
 
-By convention, `argv`**[0]** is the command with which the program is invoked.  However, it is possible to spawn a process using [CreateProcess](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-createprocessa) and if you use both the first and second arguments (`lpApplicationName` and `lpCommandLine`), `argv`**[0]** may not be the executable name; use [GetModuleFileName](https://msdn.microsoft.com/library/windows/desktop/ms683197) to retrieve the executable name.
+By convention, `argv`**[0]** is the command with which the program is invoked.  However, it is possible to spawn a process using [CreateProcess](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-createprocessa) and if you use both the first and second arguments (`lpApplicationName` and `lpCommandLine`), `argv`**[0]** may not be the executable name; use [GetModuleFileName](/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulefilenamea) to retrieve the executable name.
 
 The last pointer (`argv[argc]`) is **NULL**. (See [getenv](../c-runtime-library/reference/getenv-wgetenv.md) in the *Run-Time Library Reference* for an alternative method for getting environment variable information.)