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/ca2214-do-not-call-overridable-methods-in-constructors.md
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "CA2214: Do not call overridable methods in constructors"
3
-
ms.date: 11/04/2016
3
+
ms.date: 05/29/2016
4
4
ms.topic: reference
5
5
f1_keywords:
6
6
- "DoNotCallOverridableMethodsInConstructors"
@@ -33,7 +33,10 @@ The constructor of an unsealed type calls a virtual method defined in its class.
33
33
34
34
## Rule description
35
35
36
-
When a virtual method is called, the actual type that executes the method is not selected until run time. When a constructor calls a virtual method, it is possible that the constructor for the instance that invokes the method has not executed.
36
+
When a virtual method is called, the actual type that executes the method is not selected until run time. When a constructor calls a virtual method, it's possible that the constructor for the instance that invokes the method has not executed.
37
+
38
+
> [!NOTE]
39
+
> The binary analysis implementation of this rule has a different diagnostic message of "**\[Constructor name] contains a call chain that results in a call to a virtual method defined by the class. Review the following call stack for unintended consequences**". The [FxCop analyzers](install-fxcop-analyzers.md) implementation of this rule has a diagnostic message of "**Do not call overridable methods in constructors**".
37
40
38
41
## How to fix violations
39
42
@@ -45,7 +48,7 @@ Do not suppress a warning from this rule. The constructor should be redesigned t
45
48
46
49
## Example
47
50
48
-
The following example demonstrates the effect of violating this rule. The test application creates an instance of `DerivedType`, which causes its base class (`BadlyConstructedType`) constructor to execute. `BadlyConstructedType`'s constructor incorrectly calls the virtual method `DoSomething`. As the output shows, `DerivedType.DoSomething()` executes, and does so before `DerivedType`'s constructor executes.
51
+
The following example demonstrates the effect of violating this rule. The test application creates an instance of `DerivedType`, which causes its base class (`BadlyConstructedType`) constructor to execute. `BadlyConstructedType`'s constructor incorrectly calls the virtual method `DoSomething`. As the output shows, `DerivedType.DoSomething()` executes before `DerivedType`'s constructor executes.
Copy file name to clipboardExpand all lines: docs/get-started/csharp/tutorial-aspnet-core-ef-step-02.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,9 @@ public void OnGet()
106
106
107
107
You should now see the actual server time in the browser when you navigate to the app.
108
108
109
+
> [!NOTE]
110
+
> Your output might differ from the image, since the output format of ToShortDateTimeString depends on the current culture setting. See <xref:System.DateTime.ToShortTimeString>.
111
+
109
112

Copy file name to clipboardExpand all lines: docs/get-started/csharp/tutorial-aspnet-core.md
+15-18Lines changed: 15 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Tutorial: Get started with C# and ASP.NET Core"
3
3
titleSuffix: ""
4
4
description: "Learn how to create an ASP.NET Core web app in Visual Studio with C#, step-by-step."
5
5
ms.custom: "seodec18, get-started"
6
-
ms.date: 03/23/2019
6
+
ms.date: 05/29/2019
7
7
ms.technology: vs-ide-general
8
8
ms.prod: visual-studio-windows
9
9
ms.topic: tutorial
@@ -39,7 +39,7 @@ If you haven't already installed Visual Studio, go to the [Visual Studio downloa
39
39
40
40
### Update Visual Studio
41
41
42
-
If you've already installed Visual Studio, make sure that you are running the most recent release. For more information about how to update your installation, see the [Update Visual Studio to the most recent release](../../install/update-visual-studio.md) page.
42
+
If you've already installed Visual Studio, make sure that you're running the most recent release. For more information about how to update your installation, see the [Update Visual Studio to the most recent release](../../install/update-visual-studio.md) page.
43
43
44
44
### Choose your theme (optional)
45
45
@@ -92,7 +92,7 @@ If you don't see the **ASP.NET Core Web Application** project template, you can
92
92

93
93
94
94
> [!NOTE]
95
-
> If you don't see **ASP.NET Core 2.1**or later from the top drop-down menu, make sure that you are running the most recent release of Visual Studio. For more information about how to update your installation, see the [Update Visual Studio to the most recent release](../../install/update-visual-studio.md) page.
95
+
> If you don't see **ASP.NET Core 2.1** from the top drop-down menu, make sure that you are running the most recent release of Visual Studio. For more information about how to update your installation, see the [Update Visual Studio to the most recent release](../../install/update-visual-studio.md) page.
96
96
97
97
::: moniker-end
98
98
@@ -102,28 +102,28 @@ If you don't see the **ASP.NET Core Web Application** project template, you can
102
102
103
103

104
104
105
-
1. On the **Create a new project** window, enter or type *ASP.NET* in the search box. Next, choose **C#** from the Language list, and then choose **Windows** from the Platform list.
105
+
1. On the **Create a new project** window, enter or type *ASP.NET* in the search box. Next, choose **C#** from the Language list, and then choose **Windows** from the Platform list.
106
106
107
107
After you apply the language and platform filters, choose the **ASP.NET Core Web Application** template, and then choose **Next**.
108
108
109
109

110
110
111
111
> [!NOTE]
112
-
> If you do not see the **ASP.NET Core Web Application** 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.
112
+
> If you don't see the **ASP.NET Core Web Application** 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.
113
+
>
114
+
> 
113
115
>
114
-
> 
115
-
>
116
116
> Then, in the Visual Studio Installer, choose the **ASP.NET and web development** workload.
117
117
>
118
118
> 
119
119
>
120
-
> After that, choose the **Modify** button in the Visual Studio Installer. You might be prompted to save your work; if so, do so. Next, choose **Continue** to install the workload. Then, return to step 2 in this "[Create a project](#create-a-project)" procedure.
120
+
> After that, choose the **Modify** button in the Visual Studio Installer. If you're prompted to save your work, do so. Next, choose **Continue** to install the workload. Then, return to step 2 in this "[Create a project](#create-a-project)" procedure.
121
121
122
122
1. In the **Configure your new project** window, type or enter *MyCoreApp* in the **Project name** box. Then, choose **Create**.
123
123
124
124

125
125
126
-
1. In the **Create a new ASP.NET Core Web Application** window, verify that **ASP.NET Core 2.1**or later appears in the top drop-down menu. Then, choose **Web Application**, which includes example Razor Pages. Next, choose **Create**.
126
+
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**.
127
127
128
128

129
129
@@ -133,7 +133,7 @@ If you don't see the **ASP.NET Core Web Application** project template, you can
133
133
134
134
### About your solution
135
135
136
-
This solution follows the **Razor Page** design pattern. It is different than the [Model-View-Controller (MVC)](/aspnet/core/tutorials/first-mvc-app/start-mvc?view=aspnetcore-2.1&tabs=aspnetcore2x) design pattern in that its streamlined to include the model and controller code within the Razor Page itself.
136
+
This solution follows the **Razor Page** design pattern. It's different than the [Model-View-Controller (MVC)](/aspnet/core/tutorials/first-mvc-app/start-mvc?view=aspnetcore-2.1&tabs=aspnetcore2x) design pattern in that it's streamlined to include the model and controller code within the Razor Page itself.
137
137
138
138
## Tour your solution
139
139
@@ -176,15 +176,12 @@ This solution follows the **Razor Page** design pattern. It is different than th
176
176
> [!NOTE]
177
177
> If you get an error message that says **Unable to connect to web server 'IIS Express'**, close Visual Studio and then open it by using the **Run as administrator** option from the right-click or context menu. Then, run the application again.
178
178
>
179
-
> You might also get a message that asks if you want to accept an IIS SSL Express certificate. To view the code in a web browser, choose **Yes**, and then choose **Yes** if you receive a follow-up security warning message.
179
+
> You might also get a message that asks if you want to accept an IIS SSL Express certificate. To view the code in a web browser, choose **Yes**, and then choose **Yes** if you receive a follow-up security warning message.
180
180
181
-
1. Visual Studio launches a browser window. You should then see **Home**, **About**, and **Contact** pages in the menu bar. (If you do not, choose the "hamburger" menu item to view them.)
181
+
1. Visual Studio launches a browser window. You should then see **Home**, **About**, and **Contact** pages in the menu bar. (If you don't, choose the "hamburger" menu item to view them.)
182
182
183
183

184
184
185
-
> [!TIP]
186
-
> You cannot edit code in the Visual Studio code editor when your project is open in a browser window.
187
-
188
185
1. Choose **About** from the menu bar.
189
186
190
187

@@ -193,7 +190,7 @@ This solution follows the **Razor Page** design pattern. It is different than th
193
190
194
191

195
192
196
-
1.Keep the browser window open and return to Visual Studio.
193
+
1.Return to Visual Studio, and then press **Shift+F5**to stop Debug mode. This also closes the project in the browser window.
197
194
198
195
1. In Visual Studio, choose **About.cshtml**. Then, delete the word _additional_ and in its place, add the words _file and directory_.
199
196
@@ -217,7 +214,7 @@ This solution follows the **Razor Page** design pattern. It is different than th
title: "When package payloads change after a release"
3
+
description: "When creating a layout, learn how to determine if package payloads changed after a release has already shipped."
4
+
ms.date: 05/22/2019
5
+
ms.topic: conceptual
6
+
author: et13
7
+
ms.author: tglee
8
+
manager: jillfra
9
+
ms.workload:
10
+
- "multiple"
11
+
ms.prod: visual-studio-windows
12
+
ms.technology: vs-installation
13
+
---
14
+
# Package payload changes
15
+
16
+
Some package payloads are allowed to change after a release has already shipped. When you or someone else creates a layout, this behavior might result in different layout content, depending on when a layout was created.
17
+
18
+
## Verify that a layout includes package payload changes
19
+
20
+
Here's how to determine if the layout that was previously created has acquired the package payloads that were modified after the release shipped:
21
+
22
+
1. Open the setup log. The log is typically at `%TEMP%\dd_setup_[date].log` where `[date]` is when the layout operation started in `yyyyMMddHHmmss` format.
23
+
24
+
2. Look for a line in the log that is structured like the following text:
25
+
26
+
`Falling back to signature and signer check because hash verification returned HashMismatch for path: [path]`
27
+
28
+
3. Then, look for lines later in the log that indicate that the download succeeded for the [path]. They might look similar to the following text:
29
+
30
+
`Download of [url] succeeded using engine 'WebClient'`
31
+
32
+
`END: Downloading [url] to [path]`
33
+
34
+
## See also
35
+
36
+
*[Create a network installation of Visual Studio](create-a-network-installation-of-visual-studio.md)
37
+
*[Update a networked-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
5.Log on to the remote server if user authentication is required.
32
+
5.Sign in to the remote server if user authentication is required.
33
33
34
34
The publishing progress appears in the Visual Studio **Output** window. When the process is finished, the solution (*.wsp*) file is installed on the remote SharePoint server. However, it must still be activated before it can be used in SharePoint.
35
35
@@ -56,7 +56,7 @@ ms.workload:
56
56
57
57
7. Choose the **Publish** button.
58
58
59
-
8.Log on to the remote server if user authentication is required.
59
+
8.Sign in to the remote server if user authentication is required.
60
60
61
61
If you logged in to the remote server recently, authentication may not be required.
0 commit comments