Skip to content

Commit e680e8a

Browse files
authored
Merge pull request #3092 from MicrosoftDocs/master
10/16 AM Publish
2 parents 48bc849 + c0dc39f commit e680e8a

13 files changed

+330
-206
lines changed
-3.62 KB
Loading
13.6 KB
Loading

docs/debugger/using-breakpoints.md

Lines changed: 213 additions & 166 deletions
Large diffs are not rendered by default.

docs/deployment/tutorial-kubernetes-tools.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ ms.workload:
1414

1515
The Visual Studio Kubernetes Tools help streamline the development of containerized applications targeting Kubernetes. Visual Studio can automatically create the configuration-as-code files needed to support Kubernetes deployment, such as Dockerfiles and Helm charts. You can debug your code in a live Azure Kubernetes Service (AKS) cluster using Azure Dev Spaces, or publish directly to an AKS cluster from inside Visual Studio.
1616

17+
This tutorial covers using Visual Studio to add Kubernetes support to an project and publish to AKS. If you are primarily interested in using [Azure Dev Spaces](http://aka.ms/get-azds) to debug and test your project running in AKS, you can jump to the [Azure Dev Spaces tutorial](https://docs.microsoft.com/azure/dev-spaces/get-started-netcore-visualstudio) instead.
18+
1719
## Prerequisites
1820

1921
To leverage this new functionality, you'll need:
@@ -22,9 +24,9 @@ To leverage this new functionality, you'll need:
2224

2325
- The [Kubernetes tools for Visual Studio](https://aka.ms/get-vsk8stools), available as a separate download.
2426

25-
- [Docker for Windows](https://store.docker.com/editions/community/docker-ce-desktop-windows) installed on your development workstation (that is, where you run Visual Studio), if you wish to build Docker images, debug Docker containers running locally, or publish to AKS.
27+
- [Docker for Windows](https://store.docker.com/editions/community/docker-ce-desktop-windows) installed on your development workstation (that is, where you run Visual Studio), if you wish to build Docker images, debug Docker containers running locally, or publish to AKS. (Docker is *not* required for building and debugging Docker containers in AKS using Azure Dev Spaces.)
2628

27-
- If you wish to publish to AKS from Visual Studio:
29+
- If you wish to publish to AKS from Visual Studio (*not* required for debugging in AKS using Azure Dev Spaces):
2830

2931
1. The [AKS publishing tools](https://aka.ms/get-vsk8spublish), available as a separate download.
3032

@@ -74,11 +76,11 @@ The added files are:
7476

7577
## Publish to Azure Kubernetes Service (AKS)
7678

77-
With all these files in place, you can use the Visual Studio IDE to write and debug your application code, just as you always have.
79+
With all these files in place, you can use the Visual Studio IDE to write and debug your application code, just as you always have. You can also use [Azure Dev Spaces](http://aka.ms/get-azds) to quickly run and debug your code running live in an AKS cluster. For more information, please reference the [Azure Dev Spaces tutorial](https://docs.microsoft.com/azure/dev-spaces/get-started-netcore-visualstudio)
7880

7981
Once you have your code running the way you want, you can publish directly from Visual Studio to an AKS cluster.
8082

81-
To do this, you first need to double-check that you've installed everything as described in the [Prerequisites](#prerequisities) section under the item for publishing to AKS, and run through all the command line steps given in the links. Then, set up a publish profile that publishes your container image to Azure Container Registry (ACR). Then AKS can pull your container image from ACR and deploy it into the cluster.
83+
To do this, you first need to double-check that you've installed everything as described in the [Prerequisites](#prerequisites) section under the item for publishing to AKS, and run through all the command line steps given in the links. Then, set up a publish profile that publishes your container image to Azure Container Registry (ACR). Then AKS can pull your container image from ACR and deploy it into the cluster.
8284

8385
1. In **Solution Explorer**, right-click on your *project* and choose **Publish**.
8486

@@ -115,3 +117,5 @@ Congratulations! You can now use the full power of Visual Studio for all your Ku
115117
## Next steps
116118

117119
Learn more about Kubernetes development on Azure by reading the [AKS documentation](/azure/aks).
120+
121+
Learn more about Azure Dev Spaces by reading the [Azure Dev Spaces documentation](http://aka.ms/get-azds)

docs/designers/debugging-or-disabling-project-code-in-xaml-designer.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,19 @@ When project code is disabled, Visual Studio shows placeholders. For example, Vi
8181
> [!NOTE]
8282
> Disabling project code can lead to a loss of design-time data. An alternative is to debug the code running in the designer.
8383
84+
## Control display options
85+
86+
> [!NOTE]
87+
> **Control Display Options** is only available for Universal Windows Platform applications that target the Windows 10 Fall Creators Update (build 16299) or later. The **Control Display Options** feature is available in Visual Studio 2017 version 15.9 or later.
88+
89+
In the XAML designer, you can change your control display options to only display platform controls from the Windows SDK. This may improve reliability of the XAML designer.
90+
91+
To change control display options, click the icon in the bottom left of the designer window, and then select the **Control Display Options** button:
92+
93+
![Control Display Options](../designers/media/control_display_options.png)
94+
95+
When you select **Only Display Platform Controls**, all custom controls coming from SDKs, customer user controls, and more, will not render completely. Instead, they are replaced by fallback controls to demonstrate the size and position of the control.
96+
8497
## See also
8598

86-
- [Design XAML in Visual Studio and Blend for Visual Studio](../designers/designing-xaml-in-visual-studio.md)
99+
- [Design XAML in Visual Studio and Blend for Visual Studio](../designers/designing-xaml-in-visual-studio.md)
24.2 KB
Loading

docs/extensibility/debugger/reference/idebugcoreserver2-getmachineinfo.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,14 @@ Retrieves a description of the machine the core server is running on.
2222
## Syntax
2323

2424
```cpp
25-
HRESULT GetInfo
25+
HRESULT GetMachineInfo
2626
   MACHINE_INFO_FIELDS Fields,
2727
   MACHINE_INFO*  pMachineInfo
2828
);
2929
```
3030

3131
```csharp
32-
int GetInfo
32+
int GetMachineInfo
3333
   enum_ MACHINE_INFO_FIELDS  Fields,
3434
   MACHINE_INFO[]  pMachineInfo
3535
);
@@ -48,4 +48,4 @@ int GetInfo( 
4848
## See Also
4949
[IDebugCoreServer2](../../../extensibility/debugger/reference/idebugcoreserver2.md)
5050
[MACHINE_INFO_FIELDS](../../../extensibility/debugger/reference/machine-info-fields.md)
51-
[MACHINE_INFO](../../../extensibility/debugger/reference/machine-info.md)
51+
[MACHINE_INFO](../../../extensibility/debugger/reference/machine-info.md)

docs/extensibility/extensibility-hello-world.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload:
1212
---
1313
# Create your first extension: Hello World
1414

15-
This Hello World example walks you through creating your first extension for Visual Studio. This tutorial will show you how to add a new command to Visual Studio.
15+
This Hello World example walks you through creating your first extension for Visual Studio. This tutorial shows you how to add a new command to Visual Studio.
1616

1717
In the process, you will learn how to:
1818

@@ -29,11 +29,12 @@ For this example, you'll use Visual C# to add a custom menu button named "Say He
2929

3030
Before you start, make sure you have installed the **Visual Studio extension development** workload which includes the VSIX template you'll need and sample code.
3131

32-
Note: You can use any version of Visual Studio (Community, Professional, or Enterprise) to create a Visual Studio Extensibility project.
32+
> [!NOTE]
33+
> You can use any edition of Visual Studio (Community, Professional, or Enterprise) to create a Visual Studio extensibility project.
3334
3435
## Create an extensibility project
3536

36-
Step 1. From the **File** menu, click **New Project**. At the bottom of the screen, you can enter the name of your project.
37+
Step 1. From the **File** menu, click **New Project**. At the bottom of the screen, enter the name of your project.
3738

3839
Step 2. From the **Templates** menu, click **Visual C#**, click **Extensibility**, and then click **VSIX Project**.
3940

@@ -47,15 +48,15 @@ If you need to leave this tutorial and come back to it, you can find your new He
4748

4849
Step 1. If you select the manifest, you can see what options are changeable, for instance, metadata, description, and version.
4950

50-
Step 2. Right-click the project (not the solution). On the context menu, click **Add**, and then click **User Control**.
51+
Step 2. Right-click the project (not the solution). On the context menu, click **Add**, and then click **New Item**.
5152

52-
Step 3. Go back to the **Extensibility** section, and then click **Custom Command**.
53+
Step 3. Select the **Extensibility** section, and then click **Custom Command**.
5354

5455
Step 4. In the **Name** field at the bottom, give it a name, for instance *Command.cs*.
5556

5657
![custom command](media/hello-world-custom-command.png)
5758

58-
Your new command will be listed in the **Solution Explorer** under the **Resources** branch. This is also where you'll find other files related to your command, such as the PNG and ICO files if you wish to modify the image.
59+
Your new command is listed in **Solution Explorer** under the **Resources** branch. This is also where you'll find other files related to your command, such as the PNG and ICO files if you wish to modify the image.
5960

6061
## Modify the source code
6162

@@ -110,7 +111,7 @@ Make sure to save your changes to each file.
110111

111112
You can now run the source code in the Visual Studio Experimental Instance.
112113

113-
Step 1. Click **Start** in the Toolbar. This will build your project and start the debugger, launching a new instance of Visual Studio called the **Experimental Instance**.
114+
Step 1. Click **Start** in the Toolbar. This builds your project and starts the debugger, launching a new instance of Visual Studio called the **Experimental Instance**.
114115

115116
You will see the words **Experimental Instance** in the Visual Studio title bar.
116117

@@ -128,4 +129,4 @@ Now that you know the basics of working with Visual Studio Extensibility, here's
128129

129130
* [Start to develop Visual Studio extensions](starting-to-develop-visual-studio-extensions.md) - Samples, tutorials. and publishing your extension.
130131
* [What's new in the Visual Studio 2017 SDK](what-s-new-in-the-visual-studio-2017-sdk.md) -New extensibility features in Visual Studio 2017
131-
* [Inside the Visual Studio SDK](internals/inside-the-visual-studio-sdk.md) - Learn the details of Visual Studio Extensibility
132+
* [Inside the Visual Studio SDK](internals/inside-the-visual-studio-sdk.md) - Learn the details of Visual Studio Extensibility
23 KB
Loading

docs/ide/reference/options-text-editor-csharp-advanced.md

Lines changed: 64 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,69 @@ Use the **Advanced** options page to modify the settings for editor formatting,
2626

2727
Enables code analysis on all files in the solution, not just open code files. For more information, see [Full solution analysis](../../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md).
2828

29+
## Using Directives
30+
31+
- Place 'System' directives first when sorting usings
32+
33+
When selected, the **Remove and Sort Usings** command in the right-click menu sorts the `using` directives and places the 'System' namespaces at the top of the list
34+
35+
Before sorting:
36+
37+
```csharp
38+
using AutoMapper;
39+
using FluentValidation;
40+
using System.Collections.Generic;
41+
using System.Linq;
42+
using Newtonsoft.Json;
43+
using System;
44+
```
45+
46+
After sorting:
47+
48+
```csharp
49+
using System;
50+
using System.Collections.Generic;
51+
using System.Linq;
52+
using AutoMapper;
53+
using FluentValidation;
54+
using Newtonsoft.Json;
55+
```
56+
57+
- Separate using directive groups
58+
59+
When selected, the **Remove and Sort Usings** command in the right-click menu separates `using` directives by inserting an empty line between groups of directives that have the same root namespace.
60+
61+
Before sorting:
62+
63+
```csharp
64+
using AutoMapper;
65+
using FluentValidation;
66+
using System.Collections.Generic;
67+
using System.Linq;
68+
using Newtonsoft.Json;
69+
using System;
70+
```
71+
72+
After sorting:
73+
74+
```csharp
75+
using AutoMapper;
76+
77+
using FluentValidation;
78+
79+
using Newtonsoft.Json;
80+
81+
using System;
82+
using System.Collections.Generic;
83+
using System.Linq;
84+
```
85+
86+
- Add usings for types in reference assemblies and NuGet packages
87+
88+
When selected, a [Quick Action](../quick-actions.md) is available to install a NuGet package and add a `using` directive for unreferenced types.
89+
90+
![Quick Action to install NuGet package in Visual Studio](media/nuget-lightbulb.png)
91+
2992
## Highlighting
3093

3194
- Highlight references to symbol under cursor
@@ -50,4 +113,4 @@ Use the **Advanced** options page to modify the settings for editor formatting,
50113
- [XML Documentation Comments (C# Programming Guide)](/dotnet/csharp/programming-guide/xmldoc/xml-documentation-comments)
51114
- [Document your code with XML comments (C# Guide)](/dotnet/csharp/codedoc)
52115
- [Set language-specific editor options](../../ide/reference/setting-language-specific-editor-options.md)
53-
- [C# IntelliSense](../../ide/visual-csharp-intellisense.md)
116+
- [C# IntelliSense](../../ide/visual-csharp-intellisense.md)

docs/profiling/profiling-feature-tour.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ While you are debugging, you can use the **Diagnostic Tools** window to analyze
2828

2929
The **Diagnostic Tools** window is often the preferred way to profile apps, but for Release builds you can also do a post-mortem analysis of your app instead. If you want more information on different approaches, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). To see profiling tool support for different app types, see [Which tool should I use?](#which-tool-should-i-use).
3030

31-
> ![NOTE]
31+
> [!NOTE]
3232
> You can use the post-mortem tools with Windows 7 and later. Windows 8 and later is required to run profiling tools with the debugger (**Diagnostic Tools** window).
3333
3434
## Analyze CPU Usage
@@ -162,4 +162,4 @@ Here is a table that lists the different tools Visual Studio offers and the diff
162162
|[JavaScript Memory](../profiling/javascript-memory.md)|no|yes for HTML, no for XAML|no|
163163

164164
## See also
165-
[Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)
165+
[Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)

0 commit comments

Comments
 (0)