You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/extensibility/shell/customizing-the-isolated-shell.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,15 @@ You can customize your Visual Studio isolated shell application by changing diff
22
22
The isolated shell template solution includes a *SolutionName*.Application.pkgdef file that allows you to modify the following features:
23
23
24
24
##### The application title
25
-
You can customize the application title, which is the name that is displayed in the title bar of the application, by changing the value of the "AppName" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
25
+
You can customize the application title, which is the name that is displayed in the title bar of the application, by changing the value of the "AppName" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
26
26
27
27
If you do not want the application title to display the project that is currently loaded, change the value of the "ShowHierarchyRootInTitle" row in the *SolutionName*.Application.pkgdef file from dword:00000001 to dword:00000000.
28
28
29
29
##### The application icon
30
-
You can customize the application icon, which is the icon that is displayed by the application name in the application title bar. Copy a different icon to the icon directory. In **Solution Explorer**, add the icon to the Resource Files folder. Then open the VSShellStub.rc file and replace the value of IDI_STUBPROGRAM with the name of the new icon. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
30
+
You can customize the application icon, which is the icon that is displayed by the application name in the application title bar. Copy a different icon to the icon directory. In **Solution Explorer**, add the icon to the Resource Files folder. Then open the VSShellStub.rc file and replace the value of IDI_STUBPROGRAM with the name of the new icon. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
31
31
32
32
##### The command-line logo
33
-
You can customize the command-line logo, which is the text that appears when the application is started from the command line, by changing the value of the "CommandLineLogo" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md)
33
+
You can customize the command-line logo, which is the text that appears when the application is started from the command line, by changing the value of the "CommandLineLogo" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md)
34
34
35
35
##### The name of the user files subfolder
36
36
You can change the name of the folder your application maintains for user files by changing the value of the "UserFilesSubFolderName" row in *SolutionName*.Application.pkgdef file.
@@ -54,7 +54,7 @@ You can customize your Visual Studio isolated shell application by changing diff
54
54
You can customize the web browser page, which is page that is displayed when the web browser window is opened, by changing the value of the "DefaultSearchPage" row in the *SolutionName*.Application.pkgdef file.
55
55
56
56
##### The default home page
57
-
You can customize the home page by changing the value of the "DefaultHomePage" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md)
57
+
You can customize the home page by changing the value of the "DefaultHomePage" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md)
58
58
59
59
##### Whether or not to hide the solution concept
60
60
You can specify whether or not to hide the solution in your application by changing the value of the "HideSolutionConcept" row in the *SolutionName*.Application.pkgdef file. To hide the solution, set the value `dword:00000001`, and to show the solution, set the value `dword:00000000`.
On all the files, set the **Item Type** property to **Isolated Shell File** in order for the files to be copied to the *$RootFolder$* directory. (To set the **Item Type** property, right-click the file and select **Properties**. This property is found under **Configuration Properties**, **General**.)
104
104
105
-
For more information on customizing start pages, see [Customizing the Start Page](../ide/customizing-the-start-page-for-visual-studio.md).
105
+
For more information on customizing start pages, see [Customizing the Start Page](../../ide/customizing-the-start-page-for-visual-studio.md).
106
106
107
107
## Using other elements of the isolated shell
108
108
You can use other files and projects that are included in the isolated shell solution template to further customize your application.
removes the Miscellaneous Files project from the set of project templates displayed in the **New Project** dialog. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
117
+
removes the Miscellaneous Files project from the set of project templates displayed in the **New Project** dialog. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
118
118
119
119
##### Enable/disable menu commands
120
-
The *SolutionName*UI.vsct file includes a commented-out list of all the menu commands available to the isolated shell. To disable a given command, uncomment the corresponding row. For example, to disable the Window/Split comment, uncomment the `<Define name="No_SplitCommand"/>` row. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
120
+
The *SolutionName*UI.vsct file includes a commented-out list of all the menu commands available to the isolated shell. To disable a given command, uncomment the corresponding row. For example, to disable the Window/Split comment, uncomment the `<Define name="No_SplitCommand"/>` row. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
121
121
122
122
##### The bitmap used on the splash screen
123
-
You can customize the bitmap used on the splash screen, which is the window that is displayed when the application is started, by changing the value of the "SplashScreenBitmap" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
123
+
You can customize the bitmap used on the splash screen, which is the window that is displayed when the application is started, by changing the value of the "SplashScreenBitmap" row in the *SolutionName*.Application.pkgdef file. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
124
124
125
125
##### The Help/About window
126
-
In the isolated shell template there is a separate project you can use to customize the Help/About box for your application. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](../extensibility/walkthrough-creating-a-basic-isolated-shell-application.md).
126
+
In the isolated shell template there is a separate project you can use to customize the Help/About box for your application. For more details, see [Walkthrough: Creating a Basic Isolated Shell Application](walkthrough-creating-a-basic-isolated-shell-application.md).
Copy file name to clipboardExpand all lines: docs/extensibility/shell/distributing-isolated-shell-applications.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,11 @@ You must install Visual Studio and the Visual Studio SDK in order to create an i
20
20
21
21
|Name|Description|
22
22
|----------|-----------------|
23
-
|Visual Studio SDK|The SDK you must have to develop and test extensions of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. You can also use the SDK to create your own instance of the Visual Studio isolated shell.<br /><br /> Visual Studio is a prerequisite for the SDK.|
23
+
|Visual Studio SDK|The SDK you must have to develop and test extensions of [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. You can also use the SDK to create your own instance of the Visual Studio isolated shell.<br /><br /> Visual Studio is a prerequisite for the SDK.|
24
24
|Microsoft Visual Studio Isolated Shell Redistributable|The redistributable that you include in your Setup program when you build a tools environment on the Visual Studio isolated shell. The isolated Shell redistributable package includes the .NET Framework 4.5.|
25
25
26
26
## Creating an Installation Program for the Application
27
-
You must create a special installation program for your integrated or isolated shell application. For more information, see [Installing an Isolated Shell Application](../extensibility/installing-an-isolated-shell-application.md).
27
+
You must create a special installation program for your integrated or isolated shell application. For more information, see [Installing an Isolated Shell Application](installing-an-isolated-shell-application.md).
28
28
29
29
## Allowing for Updates to your Application
30
-
Your installation program must allow for the possibility that your application will be updated, either by Microsoft updates or by your company's updates. For more information about updates, see [Servicing Guidelines for Isolated Shell Applications](../extensibility/servicing-guidelines-for-isolated-shell-applications.md).
30
+
Your installation program must allow for the possibility that your application will be updated, either by Microsoft updates or by your company's updates. For more information about updates, see [Servicing Guidelines for Isolated Shell Applications](servicing-guidelines-for-isolated-shell-applications.md).
|Designer|- Windows Presentation Foundation Designer<br />- Windows Forms Designer<br />- Web Designer and HTML Editor|
40
-
|Data|- **Server Explorer** (Simplified: data only). See Note 1.<br />- **Data Sources** window<br />- Full set of data controls<br />- XML Editor<br />- Data bind to local data source (.MDF or .MDB)<br />- Data bind to object<br />- Data bind to Web service<br />- Data bind to local database server<br />- Data bind to remote database server<br />- DDL tools for remote data<br />- **Server Explorer** extensibility ([!INCLUDE[vsipsdk](../extensibility/includes/vsipsdk_md.md)] samples)|
40
+
|Data|- **Server Explorer** (Simplified: data only). See Note 1.<br />- **Data Sources** window<br />- Full set of data controls<br />- XML Editor<br />- Data bind to local data source (.MDF or .MDB)<br />- Data bind to object<br />- Data bind to Web service<br />- Data bind to local database server<br />- Data bind to remote database server<br />- DDL tools for remote data<br />- **Server Explorer** extensibility ([!INCLUDE[vsipsdk](../includes/vsipsdk_md.md)] samples)|
41
41
|Debugger|- Local debugging. See Note 2.<br />- Managed debugging<br />- Local debugging<br />- Attach to local process<br />- Attach to remote process<br />- Anonymous delegate<br />- Application domains<br />- ASPX Debugging<br />- Attributes<br />- Break during Func-eval<br />- Breakpoints<br />- Breakpoint constraints<br />- Callstack<br />- **Command** window<br />- Cross-thread debugging<br />- Data Tips<br />- Data visualizer<br />- Debugger support for managed debugging assistants (MDAs)<br />- Debugger support for type forwarder<br />- DTEEvents support for OTB<br />- JMC Stepper<br />- Debugger AppID test (DBGCLR)<br />- Debugger profile<br />- Debugger tools and options<br />- Debugging iterator<br />- Design-time expression evaluation<br />- C# Expression Evaluator<br />- Disassembly<br />- Edit and Continue<br />- Expression evaluator windows (Watch, Locals, Autos)<br />- Exception Helper<br />- Exceptions<br />- Execution<br />- Generics<br />- Getting right source<br />- HPC/Cluster debugging<br />- Integrated multi-language debugging<br />- InterOp debugging<br />- Just-in-time debugging<br />- Local debugging<br />- Managed debugging<br />- Manual control (Processes window)<br />- Memory<br />- MiniDump support<br />- Modules<br />- Multi-process debugging<br />- Native debugging<br />- New debug engine support<br />- Optimized code debugging<br />- Output windows filtering<br />- Process hosting for managed debugging<br />- Processes<br />- Quickwatch<br />- Registers<br />- Registers in stack<br />- Remote debugging<br />- Return values<br />- Script debugging<br />- Source service support<br />- Security<br />- Side-by-side<br />- SQL<br />- Symbol server<br />- Trace points<br />- Thread<br />- Visualizations<br />- Extensible Stylesheet Language Transformations (XSLT) debugger|
42
42
|64-bit Support|- 64-bit debugging for both managed and native code, all languages<br />- x64 native support|
43
43
|Source Code Control (SCC)|- Basic SCC integration. See Note 3.<br />- Tools and options verification|
@@ -59,14 +59,14 @@ The Visual Studio integrated shell includes the integrated development environme
59
59
Although SCC integration is not a regular feature of the Pro edition of Visual Studio, SCC integration is provided in the integrated shell.
60
60
61
61
#### 4. Build Support
62
-
The integrated shell provides build support. You can find information about builds in the [MSBuild Reference](../msbuild/msbuild-reference.md).
62
+
The integrated shell provides build support. You can find information about builds in the [MSBuild Reference](../../msbuild/msbuild-reference.md).
63
63
64
64
## Features Not Included in the Integrated Shell
65
65
The following is a list of features that are not included in the integrated shell:
@@ -75,4 +75,4 @@ The Visual Studio integrated shell includes the integrated development environme
75
75
- No Visual Studio languages or their associated project templates or project item templates, are included in the integrated shell. No language-specific implementations of other features are included, for example Visual Basic code snippets.
76
76
77
77
## See Also
78
-
[Visual Studio SDK](../extensibility/visual-studio-sdk.md)
0 commit comments