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/code-quality/ca1026-default-parameters-should-not-be-used.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,9 @@ ms.workload:
27
27
## Cause
28
28
An externally visible type contains an externally visible method that uses a default parameter.
29
29
30
+
> [!NOTE]
31
+
> This legacy rule is not available in FxCop Analyzers. For more information, see [Deprecated rules](fxcop-rule-port-status.md#deprecated-rules).
32
+
30
33
## Rule description
31
34
Methods that use default parameters are allowed under the Common Language Specification (CLS); however, the CLS allows compilers to ignore the values that are assigned to these parameters. Code that is written for compilers that ignore default parameter values must explicitly provide arguments for each default parameter. To maintain the behavior that you want across programming languages, methods that use default parameters should be replaced with method overloads that provide the default parameters.
> Although <xref:System.Xml.XmlReader.Create%2A?displayProperty=nameWithType> is the recommended way to create an <xref:System.Xml.XmlReader> instance, there are behavior differences from <xref:System.Xml.XmlTextReader>. An <xref:System.Xml.XmlReader> from <xref:System.Xml.XmlReader.Create%2A> normalizes `\r\n` to `\n` in XML values, while <xref:System.Xml.XmlTextReader> preserves the `\r\n` sequence.
The next step is different depending on whether you're using Linux containers or Windows containers.
64
+
65
+
## Modify the Dockerfile (Linux containers)
60
66
61
67
A *Dockerfile*, the recipe for creating a final Docker image, is created in the project. Refer to [Dockerfile reference](https://docs.docker.com/engine/reference/builder/) for an understanding of the commands within it.
62
68
@@ -98,9 +104,74 @@ The preceding *Dockerfile* is based on the [microsoft/aspnetcore](https://hub.do
98
104
99
105
When the new project dialog's **Configure for HTTPS** check box is checked, the *Dockerfile* exposes two ports. One port is used for HTTP traffic; the other port is used for HTTPS. If the check box isn't checked, a single port (80) is exposed for HTTP traffic.
100
106
107
+
## Modify the Dockerfile (Windows containers)
108
+
109
+
Open the project file by double-clicking on the project node, and update the project file (*.csproj) by adding the following property as a child of the `<PropertyGroup>` element:
1. The complete Dockerfile should now look something like this:
135
+
136
+
```
137
+
# escape=`
138
+
#Depending on the operating system of the host machines(s) that will build or run the containers, the image specified in the FROM statement may need to be changed.
139
+
#For more information, please see https://aka.ms/containercompat
140
+
FROM mcr.microsoft.com/powershell:nanoserver-1903 AS downloadnodejs
RUN dotnet restore "WebApplication7/WebApplication7.csproj"
157
+
COPY . .
158
+
WORKDIR "/src/WebApplication37"
159
+
RUN dotnet build "WebApplication37.csproj" -c Release -o /app/build
160
+
161
+
FROM build AS publish
162
+
RUN dotnet publish "WebApplication37.csproj" -c Release -o /app/publish
163
+
164
+
FROM base AS final
165
+
WORKDIR /app
166
+
COPY --from=publish /app/publish .
167
+
ENTRYPOINT ["dotnet", "WebApplication37.dll"]
168
+
```
169
+
170
+
1. Update the .dockerignore file by removing the `**/bin`.
171
+
101
172
## Debug
102
173
103
-
Select **Docker** from the debug drop-down in the toolbar, and start debugging the app. You might see a message with a prompt about trusting a certificate; choose to trust the certificate to continue.
174
+
Select **Docker** from the debug drop-down in the toolbar, and start debugging the app. You might see a message with a prompt about trusting a certificate; choose to trust the certificate to continue. The first time you build, docker downloads the base images, so it might take a bit longer.
104
175
105
176
The **Container Tools** option in the **Output** window shows what actions are taking place. You should see the installation steps associated with *npm.exe*.
Copy file name to clipboardExpand all lines: docs/debugger/using-tracepoints.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ The behavior of the **When changed** option is different for different program
98
98
- For native code, the debugger doesn't consider the first evaluation of the condition to be a change, so doesn't hit the tracepoint on the first evaluation.
99
99
- For managed code, the debugger hits the tracepoint on the first evaluation after **When changed** is selected.
100
100
101
-
For a more comprehensive look at valid expressions you can use while setting conditions, see [Expressions in the debugger](expressions-in-the-debugger.md)
101
+
For a more comprehensive look at valid expressions you can use while setting conditions, see [Expressions in the debugger](expressions-in-the-debugger.md).
102
102
103
103
### Hit count
104
104
A hit count condition allows you to send output only after the line of code where the tracepoint is set has executed a specified number of times.
@@ -130,10 +130,13 @@ Sometimes when you inspect a property or attribute of an object, its value can c
130
130
131
131
The way that expressions are evaluated in the **Action** message box may be different than the language you are currently using for development. For example, to output a string you do not need to wrap a message in quotes even if you normally would while using `Debug.WriteLine()` or `console.log()`. Also, the curly brace syntax (`{ }`) to output expressions may also be different than the convention for outputting values in your development language. (However, the contents within the curly braces (`{ }`) should still be written using your development language’s syntax).
132
132
133
+
If you are trying to debug a live application and looking for a similar feature, check out our logpoint feature in the Snapshot Debugger. The snapshot debugger is a tool used to investigate issues in production applications. Logpoints also allow you to send messages to the Output Window without having to modify source code and do not impact your running application. For more information, see [Debug live Azure application](../debugger/debug-live-azure-applications.md).
134
+
133
135
## See also
134
136
135
137
-[What is debugging?](../debugger/what-is-debugging.md)
136
138
-[Write better C# code using Visual Studio](../debugger/write-better-code-with-visual-studio.md)
137
139
-[First look at debugging](../debugger/debugger-feature-tour.md)
138
140
-[Expressions in the debugger](expressions-in-the-debugger.md)
Copy file name to clipboardExpand all lines: docs/ide/quickstart-aspnet-core.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Create an ASP.NET Core web app in C#"
3
3
description: "Learn how to create a simple Hello World web app in Visual Studio with C# and ASP.NET Core, step-by-step."
4
4
ms.custom: "mvc,seodec18"
5
-
ms.date: 06/06/2019
5
+
ms.date: 10/15/2019
6
6
ms.technology: vs-ide-general
7
7
ms.prod: visual-studio-windows
8
8
ms.topic: quickstart
@@ -104,9 +104,9 @@ Soon after, Visual Studio opens your project file.
104
104
105
105
106
106
107
-
1. In the **Create a new ASP.NET Core Web Application** window, verify that **ASP.NET Core 2.1** appears in the top drop-down menu. Then, choose **Web Application**, which includes example Razor Pages. Next, choose **Create**.
107
+
1. In the **Create a new ASP.NET Core Web Application** window, verify that **ASP.NET Core 3.0** appears in the top drop-down menu. Then, choose **Web Application**, which includes example Razor Pages. Next, choose **Create**.
108
108
109
-
109
+
Copy file name to clipboardExpand all lines: docs/ide/step-1-create-a-project-and-add-a-table-to-your-form.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Step 1: Create a project and add a table to your form"
3
-
ms.date: 05/31/2019
3
+
ms.date: 10/15/2019
4
4
ms.topic: tutorial
5
5
ms.prod: visual-studio-windows
6
6
ms.technology: vs-ide-general
@@ -38,11 +38,11 @@ The first step in creating a matching game is to create the project and add a ta
38
38
39
39
40
40
41
-
1. On the **Create a new project** window, enter or type *Windows Forms* in the search box.
41
+
1. On the **Create a new project** window, enter or type *Windows Forms* in the search box. Next, choose **Desktop** from the **Project type** list.
42
42
43
-
1. Choose the **Windows Forms App (.NET Framework)** template, and then choose **Next**.
43
+
After you apply the **Project type** filter, choose the **Windows Forms App (.NET Framework)** template for either C# or Visual Basic, and then choose **Next**.
44
44
45
-
45
+
46
46
47
47
> [!NOTE]
48
48
> If you do not see the **Windows Forms App (.NET Framework)** template, you can install it from the **Create a new project** window. In the **Not finding what you're looking for?** message, choose the **Install more tools and features** link.
Copy file name to clipboardExpand all lines: docs/ide/step-1-create-a-project-and-add-labels-to-your-form.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Step 1: Create a project and add labels to your form"
3
-
ms.date: 05/31/2019
3
+
ms.date: 10/15/2019
4
4
ms.topic: tutorial
5
5
ms.prod: visual-studio-windows
6
6
ms.technology: vs-ide-general
@@ -43,11 +43,11 @@ As the first steps in developing this quiz, you create the project, and you add
43
43
44
44
45
45
46
-
1. On the **Create a new project** window, enter or type *Windows Forms* in the search box.
46
+
1. On the **Create a new project** window, enter or type *Windows Forms* in the search box. Next, choose **Desktop** from the **Project type** list.
47
47
48
-
1. Choose the **Windows Forms App (.NET Framework)** template, and then choose **Next**.
48
+
After you apply the **Project type** filter, choose the **Windows Forms App (.NET Framework)** template for either C# or Visual Basic, and then choose **Next**.
49
49
50
-
50
+
51
51
52
52
> [!NOTE]
53
53
> If you do not see the **Windows Forms App (.NET Framework)** template, you can install it from the **Create a new project** window. In the **Not finding what you're looking for?** message, choose the **Install more tools and features** link.
Copy file name to clipboardExpand all lines: docs/ide/step-1-create-a-windows-forms-application-project.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ When you create a picture viewer, the first step is to create a Windows Forms Ap
44
44
45
45
After you apply the **Project type** filter, choose the **Windows Forms App (.NET Framework)** template for either C# or Visual Basic, and then choose **Next**.
46
46
47
-
47
+
48
48
49
49
> [!NOTE]
50
50
> If you don't see the **Windows Forms App (.NET Framework)** template, you can install it from the **Create a new project** window. In the **Not finding what you're looking for?** message, choose the **Install more tools and features** link.
Copy file name to clipboardExpand all lines: docs/ide/step-2-add-a-random-object-and-a-list-of-icons.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,12 @@ ms.workload:
15
15
- "multiple"
16
16
---
17
17
# Step 2: Add a Random object and a list of icons
18
+
18
19
In this step, you create a set of matching symbols for the game. Each symbol is added to two random cells in the TableLayoutPanel on the form. To do this, you use two `new` statements to create two objects. The first is a <xref:System.Random> object, like the one you used in the math quiz game. It is used in this code to randomly choose cells in the TableLayoutPanel. The second object, which may be new to you, is a <xref:System.Collections.Generic.List%601> object which is used to store the randomly-chosen symbols.
19
20
20
21
## To add a random object and a list of icons
21
22
22
-
1. In **Solution Explorer**, choose *Form1.cs* if you're using Visual C#, or *Form1.vb* if you're using Visual Basic, and then on the menu bar, choose **View** > **Code**. As an alternative, you can choose the **F7** key or double-click **Form1** in **Solution Explorer**.
23
+
1. In **Solution Explorer**, choose *Form1.cs* if you're using C#, or *Form1.vb* if you're using Visual Basic, and then on the menu bar, choose **View** > **Code**. As an alternative, you can choose the **F7** key or double-click **Form1** in **Solution Explorer**.
23
24
24
25
This displays the code module behind Form1.
25
26
@@ -35,8 +36,7 @@ In this step, you create a set of matching symbols for the game. Each symbol is
35
36
36
37
3. When adding the List object, notice the **IntelliSense** window that opens. The following is a Visual C# example, but similar text appears when you add a list in Visual Basic.
> The IntelliSense window appears only when you enter code manually. If you copy and paste the code, it doesn't appear.
@@ -54,6 +54,6 @@ IntelliSense window
54
54
55
55
## To continue or review
56
56
57
-
- To go to the next tutorial step, see [Step 3: Assign a random icon to each label](../ide/step-3-assign-a-random-icon-to-each-label.md).
57
+
- To go to the next tutorial step, see [**Step 3: Assign a random icon to each label**](../ide/step-3-assign-a-random-icon-to-each-label.md).
58
58
59
59
- To return to the previous tutorial step, see [Step 1: Create a project and add a table to your form](../ide/step-1-create-a-project-and-add-a-table-to-your-form.md).
0 commit comments