Fix more broken links

Author: ghogen

docs/extensibility/shell/elements-of-the-isolated-shell.md

@@ -40,28 +40,28 @@ You can modify the registry settings, run-time settings, and application entry p
 
 2.  If neither the registry nor the entry point parameter specifies the value of a setting, then the default value for the setting is used.  
 
- When a user starts your application from the command line, all command-line switches are passed to the Visual Studio shell, which treats them in the same way that Devenv does. For more information about Devenv switches, see [Devenv Command Line Switches](../ide/reference/devenv-command-line-switches.md) and [Devenv Command-Line Switches for VSPackage Development](../extensibility/devenv-command-line-switches-for-vspackage-development.md). For more information about how a package registers for command line switches, see [Adding Command-Line Switches](../extensibility/adding-command-line-switches.md).  
+ When a user starts your application from the command line, all command-line switches are passed to the Visual Studio shell, which treats them in the same way that Devenv does. For more information about Devenv switches, see [Devenv Command Line Switches](../../ide/reference/devenv-command-line-switches.md) and [Devenv Command-Line Switches for VSPackage Development](../devenv-command-line-switches-for-vspackage-development.md). For more information about how a package registers for command line switches, see [Adding Command-Line Switches](../adding-command-line-switches.md).  
 
 ## The Start Entry Point  
  The Appenvstub.dll file contains entry points for accessing the isolated shell. When the application starts, it calls the Start entry point of Appenvstub.dll.  
 
- You can change the behavior of the application by changing the value of the last parameter that is passed to the Start entry point. For more information, see [Isolated Shell Entry Point Parameters (C++)](../extensibility/isolated-shell-entry-point-parameters-cpp.md).  
+ You can change the behavior of the application by changing the value of the last parameter that is passed to the Start entry point. For more information, see [Isolated Shell Entry Point Parameters (C++)](isolated-shell-entry-point-parameters-cpp.md).  
 
 ## The .Vsct File  
- The .vsct file lets you specify which standard Visual Studio UI elements are available in the application. For more information, see [.Vsct Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-vsct-file.md).  
+ The .vsct file lets you specify which standard Visual Studio UI elements are available in the application. For more information, see [.Vsct Files](modifying-the-isolated-shell-by-using-the-dot-vsct-file.md).  
 
 ## The .Pkgundef File  
- When the application is installed on a computer on which Visual Studio is already installed, a copy of the Visual Studio registry entries is made for the application. By default, the application uses VSPackages that are already installed on the computer. The .pkgundef file lets you exclude registry entries in order to remove specific elements of the Visual Studio shell or extensions from the application. For more information, see [.Pkgundef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md).  
+ When the application is installed on a computer on which Visual Studio is already installed, a copy of the Visual Studio registry entries is made for the application. By default, the application uses VSPackages that are already installed on the computer. The .pkgundef file lets you exclude registry entries in order to remove specific elements of the Visual Studio shell or extensions from the application. For more information, see [.Pkgundef Files](modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md).  
 
- The .pkgundef file lets you exclude registry entries in order to remove specific elements of the Visual Studio shell or extensions from the application. For more information, see [.Pkgundef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md).  
+ The .pkgundef file lets you exclude registry entries in order to remove specific elements of the Visual Studio shell or extensions from the application. For more information, see [.Pkgundef Files](modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md).  
 
- The set of package GUIDs that you can exclude are listed in [Package GUIDs of Visual Studio Features](../extensibility/package-guids-of-visual-studio-features.md).  
+ The set of package GUIDs that you can exclude are listed in [Package GUIDs of Visual Studio Features](package-guids-of-visual-studio-features.md).  
 
 ## The .Pkgdef File  
- The .pkgdef file lets you define registry entries for the application that are set when the application is installed. For a description of the .pkgdef file and a list of registry entries that the Visual Studio shell uses, see [.Pkgdef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md).  
+ The .pkgdef file lets you define registry entries for the application that are set when the application is installed. For a description of the .pkgdef file and a list of registry entries that the Visual Studio shell uses, see [.Pkgdef Files](modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md).  
 
 ## Substitution Strings  
- The substitution strings used in the .pkgdef and .pkgundef files are listed in [Substitution Strings Used in .Pkgdef and .Pkgundef Files](../extensibility/substitution-strings-used-in-dot-pkgdef-and-dot-pkgundef-files.md).  
+ The substitution strings used in the .pkgdef and .pkgundef files are listed in [Substitution Strings Used in .Pkgdef and .Pkgundef Files](substitution-strings-used-in-dot-pkgdef-and-dot-pkgundef-files.md).  
 
 ## Other Settings  
  If your isolated shell application depends on Microsoft.VisualStudio.GraphModel.dll, you need to add the following binding redirect to your Isolated Shell application's .config file:  

docs/extensibility/shell/extending-the-isolated-shell.md

@@ -19,7 +19,7 @@ manager: "ghogen"
 You can extend the Visual Studio isolated shell by adding a VSPackage, a Managed Extensibility Framework (MEF) component part, or a generic VSIX project to your isolated shell application.  
 
 > [!NOTE]
->  The following steps presuppose that you have created a basic isolated shell application by using the Visual Studio Shell Isolated project template. For more information about this project template, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).  
+>  The following steps presuppose that you have created a basic isolated shell application by using the Visual Studio Shell Isolated project template. For more information about this project template, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).  
   
 ## Locations for the Visual Studio Package Project Template  
  The Visual Studio Package project template can be found in three different locations in the **New Project** dialog:  
@@ -117,4 +117,4 @@ You can extend the Visual Studio isolated shell by adding a VSPackage, a Managed
 8.  Build and run the solution.  
 
 ## See Also  
- [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md)
+ [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md)

docs/extensibility/shell/installing-an-isolated-shell-application.md

@@ -365,4 +365,4 @@ dwResult = ExecCmd(boutiqueInstallCmd, FALSE);
 ```  
 
 ## See Also  
- [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md)
+ [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md)

docs/extensibility/shell/isolated-shell-entry-point-parameters-cpp.md

@@ -17,7 +17,7 @@ ms.author: "gregvanl"
 manager: "ghogen"
 ---
 # Isolated Shell Entry Point Parameters (C++)
-When a Visual Studio shell-based application starts, it calls the Start entry point of the Visual Studio shell. The following settings can be overridden in the call to the Start entry point of the shell. For a description of each setting, see [.Pkgdef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md).  
+When a Visual Studio shell-based application starts, it calls the Start entry point of the Visual Studio shell. The following settings can be overridden in the call to the Start entry point of the shell. For a description of each setting, see [.Pkgdef Files](modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md).  
 
 -   AddinsAllowed  
 
@@ -91,5 +91,5 @@ typedef int (__cdecl *STARTFCN)(LPSTR, LPWSTR, int, GUID *, WCHAR *pszSettings);
  To disable add-ins and change the default projects location for your application, you can set the last parameter to "AddinsAllowed=false;DefaultProjectsLocation=%USERPROFILE%\temp".  
 
 ## See Also  
- [Customizing the Isolated Shell](../extensibility/customizing-the-isolated-shell.md)   
- [.Pkgdef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md)
+ [Customizing the Isolated Shell](customizing-the-isolated-shell.md)   
+ [.Pkgdef Files](modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md)

docs/extensibility/shell/modifying-the-isolated-shell-by-using-the-dot-pkgdef-file.md

@@ -44,7 +44,7 @@ The .pkgdef file supports settings that you can use to customize an isolated she
 
  You can add comments to the .pkgdef file. A single-line comment has two slashes as the first two characters.  
 
- For a list of the substitution strings, see [Substitution Strings Used in .Pkgdef and .Pkgundef Files](../extensibility/substitution-strings-used-in-dot-pkgdef-and-dot-pkgundef-files.md).  
+ For a list of the substitution strings, see [Substitution Strings Used in .Pkgdef and .Pkgundef Files](substitution-strings-used-in-dot-pkgdef-and-dot-pkgundef-files.md).  
 
  The following sections describe specific registry values that affect the behavior of the Visual Studio shell in isolated mode. You can also define additional registry values for the application in this file.  
 
@@ -63,12 +63,12 @@ The .pkgdef file supports settings that you can use to customize an isolated she
 |AppName|string|The name of the application. The name appears in the title bar of the application window.<br /><br /> The default value is the name of the application solution file.|  
 |CommandLineLogo|string|The banner text when the application is run in a console window. This setting affects only applications that support command-line build operations.<br /><br /> The default value is "*companyName**solutionName* Version 1.0.", where *companyName* is the name of the company provided when Windows was installed, and *solutionName* is the name of the application solution file.|  
 |DefaultDebugEngine|string|The GUID of the default debug engine to use for the application.<br /><br /> Note: An empty GUID (all zeros) indicates that the application does not specify a default debug engine. This enables the debugger to select the debug engine to use.<br /><br /> The default value is "{00000000-0000-0000-0000-000000000000}".|  
-|DefaultHomePage|string|The default home page URL for the internal Web browser window.<br /><br /> If the **Home page** option is available in the application, then this setting also affects the default state of the option. For more information, see [Web Browser, Environment, Options Dialog Box](../ide/reference/web-browser-environment-options-dialog-box.md).<br /><br /> The default value is the URL of the company provided when Windows was installed.|  
+|DefaultHomePage|string|The default home page URL for the internal Web browser window.<br /><br /> If the **Home page** option is available in the application, then this setting also affects the default state of the option. For more information, see [Web Browser, Environment, Options Dialog Box](../../ide/reference/web-browser-environment-options-dialog-box.md).<br /><br /> The default value is the URL of the company provided when Windows was installed.|  
 |DefaultProjectsLocation|string|The full path of the default projects folder. For example,<br /><br /> `"DefaultProjectsLocation"="$MyDocuments$\MyVSShellStub\Projects"`<br /><br /> If the **Visual Studio projects location** option is available in the application, then this setting also affects the default state of the option. For more information, see [NIB: General, Projects and Solutions, Options Dialog Box](http://msdn.microsoft.com/en-us/8f8e37e8-b28d-4b13-bfeb-ea4d3312aeca).<br /><br /> The default value is "$MyDocuments$\\*solutionName*", where *solutionName* is the name of the application solution file.|  
-|DefaultSearchPage|string|The default search page URL for the internal Web browser window.<br /><br /> If the **Search page** option is available in the application, then this setting also affects the default state of the option. For more information, see [Web Browser, Environment, Options Dialog Box](../ide/reference/web-browser-environment-options-dialog-box.md).<br /><br /> The default value is "http://search.live.com".|  
+|DefaultSearchPage|string|The default search page URL for the internal Web browser window.<br /><br /> If the **Search page** option is available in the application, then this setting also affects the default state of the option. For more information, see [Web Browser, Environment, Options Dialog Box](../../ide/reference/web-browser-environment-options-dialog-box.md).<br /><br /> The default value is "http://search.live.com".|  
 |DefaultUserFilesFolderRoot|string|The name of the user folder, relative to the current user's My Documents folder.<br /><br /> The default value is the name of the application solution file.|  
 |DisableOutputWindow|dword|Indicates whether the isolated shell should treat the output window as disabled.<br /><br /> If this value is set to true, Visual Studio does not display the solution build manager output in the **Output** window and hides the **Show Output window when build starts** check box in the **Projects and Solutions** category in the **Options** dialog box.<br /><br /> The default value is false.|  
-|HideMiscellaneousFilesByDefault|dword|True to hide the **Miscellaneous Files** folder by default in **Solution Explorer**; otherwise, false.<br /><br /> If the **Show Miscellaneous files in Solution Explorer** option is available in the application, then this setting also affects the default state of the option. For more information, see [Documents, Environment, Options Dialog Box](../ide/reference/documents-environment-options-dialog-box.md).<br /><br /> The default value is false.|  
+|HideMiscellaneousFilesByDefault|dword|True to hide the **Miscellaneous Files** folder by default in **Solution Explorer**; otherwise, false.<br /><br /> If the **Show Miscellaneous files in Solution Explorer** option is available in the application, then this setting also affects the default state of the option. For more information, see [Documents, Environment, Options Dialog Box](../../ide/reference/documents-environment-options-dialog-box.md).<br /><br /> The default value is false.|  
 |HideSolutionConcept|dword|True to create all projects as stand-alone projects and hide the solution and solution-related commands for stand-alone projects by default; otherwise, false.<br /><br /> If the **Always show solution** option is available in the application, then this setting also affects the default state of the option. For more information, see [NIB: General, Projects and Solutions, Options Dialog Box](http://msdn.microsoft.com/en-us/8f8e37e8-b28d-4b13-bfeb-ea4d3312aeca).<br /><br /> The default value is false.|  
 |NewProjDlgInstalledTemplatesHdr|string|The name for the Visual Studio nstalled templates header in the **Templates** list in the **New Project** dialog box. This is either a string or a localizable resource identifier that is loaded from the application UI package.<br /><br /> The default value is "*solutionName* installed templates", where *solutionName* is the name of the application solution file.|  
 |NewProjDlgSlnTreeNodeTitle|string|The name for the **Visual Studio Solutions** node in the **Project types** tree in the **New Project** dialog box. This is either a string or a localizable resource identifier that is loaded from the application UI package.<br /><br /> The default value is "*solutionName* installed templates", where *solutionName* is the name of the application solution file.|  
@@ -117,12 +117,12 @@ The .pkgdef file supports settings that you can use to customize an isolated she
 ## Package Menu Item Settings  
  The [$RootKey$\Menus] registry key defines UI resource files for the application.  
 
- Menu item values have the form "{*vsUiPackageGuid*}"=", *resourceId*, *versionNumber*", where *vsUiPackageGuid* is the GUID of the application UI package, *resourceId* is the resource identifier of the CTMENU resource that contains the UI elements, and *versionNumber* is a virtual version number for the CTMENU resource. For more information, see [Registering Interop Assembly Command Handlers](../extensibility/internals/registering-interop-assembly-command-handlers.md).  
+ Menu item values have the form "{*vsUiPackageGuid*}"=", *resourceId*, *versionNumber*", where *vsUiPackageGuid* is the GUID of the application UI package, *resourceId* is the resource identifier of the CTMENU resource that contains the UI elements, and *versionNumber* is a virtual version number for the CTMENU resource. For more information, see [Registering Interop Assembly Command Handlers](../internals/registering-interop-assembly-command-handlers.md).  
 
  By default, a menu item entry is created in the .pkgdef file for the application UI package.  
 
  For each package that provides menu items and that is distributed as a part of the application, add a menu item entry for the package.  
 
 ## See Also  
- [Customizing the Isolated Shell](../extensibility/customizing-the-isolated-shell.md)   
- [.Pkgundef Files](../extensibility/modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md)
+ [Customizing the Isolated Shell](customizing-the-isolated-shell.md)   
+ [.Pkgundef Files](modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md)

docs/extensibility/shell/modifying-the-isolated-shell-by-using-the-dot-pkgundef-file.md

@@ -41,5 +41,5 @@ You can modify the .pkgundef file to exclude specified registry entries from an
  to the application's .pkgundef file.  
 
 ## See Also  
- [Package GUIDs of Visual Studio Features](../extensibility/package-guids-of-visual-studio-features.md)   
- [Customizing the Isolated Shell](../extensibility/customizing-the-isolated-shell.md)
+ [Package GUIDs of Visual Studio Features](package-guids-of-visual-studio-features.md)   
+ [Customizing the Isolated Shell](customizing-the-isolated-shell.md)