Skip to content

Commit e3d96b2

Browse files
authored
Merge pull request #3795 from MicrosoftDocs/master
1/31/2019 AM Publish
2 parents 9866740 + c6531cd commit e3d96b2

File tree

69 files changed

+363
-233
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+363
-233
lines changed

docs/code-quality/ca1820-test-for-empty-strings-using-string-length.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -26,20 +26,25 @@ ms.workload:
2626
|Breaking Change|Non-breaking|
2727

2828
## Cause
29-
A string is compared to the empty string by using <xref:System.Object.Equals%2A?displayProperty=fullName>.
29+
30+
A string is compared to the empty string by using <xref:System.Object.Equals%2A?displayProperty=nameWithType>.
3031

3132
## Rule description
32-
Comparing strings using the <xref:System.String.Length%2A?displayProperty=fullName> property or the <xref:System.String.IsNullOrEmpty%2A?displayProperty=fullName> method is significantly faster than using <xref:System.Object.Equals%2A>. This is because <xref:System.Object.Equals%2A> executes significantly more MSIL instructions than either <xref:System.String.IsNullOrEmpty%2A> or the number of instructions executed to retrieve the <xref:System.String.Length%2A> property value and compare it to zero.
3333

34-
You should be aware that <xref:System.Object.Equals%2A> and <xref:System.String.Length%2A> == 0 behave differently for null strings. If you try to get the value of the <xref:System.String.Length%2A> property on a null string, the common language runtime throws a <xref:System.NullReferenceException?displayProperty=fullName>. If you perform a comparison between a null string and the empty string, the common language runtime does not throw an exception; the comparison returns `false`. Testing for null does not significantly affect the relative performance of these two approaches. When targeting [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)], use the <xref:System.String.IsNullOrEmpty%2A> method. Otherwise, use the <xref:System.String.Length%2A> == comparison whenever possible.
34+
Comparing strings using the <xref:System.String.Length%2A?displayProperty=nameWithType> property or the <xref:System.String.IsNullOrEmpty%2A?displayProperty=nameWithType> method is faster than using <xref:System.Object.Equals%2A>. This is because <xref:System.Object.Equals%2A> executes significantly more MSIL instructions than either <xref:System.String.IsNullOrEmpty%2A> or the number of instructions executed to retrieve the <xref:System.String.Length%2A> property value and compare it to zero.
35+
36+
For null strings, <xref:System.Object.Equals%2A> and <xref:System.String.Length%2A> == 0 behave differently. If you try to get the value of the <xref:System.String.Length%2A> property on a null string, the common language runtime throws a <xref:System.NullReferenceException?displayProperty=fullName>. If you perform a comparison between a null string and the empty string, the common language runtime does not throw an exception and returns `false`. Testing for null does not significantly affect the relative performance of these two approaches. When targeting .NET Framework 2.0 or later, use the <xref:System.String.IsNullOrEmpty%2A> method. Otherwise, use the <xref:System.String.Length%2A> == 0 comparison whenever possible.
3537

3638
## How to fix violations
37-
To fix a violation of this rule, change the comparison to use the <xref:System.String.Length%2A> property and test for the null string. If targeting [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)], use the <xref:System.String.IsNullOrEmpty%2A> method.
39+
40+
To fix a violation of this rule, change the comparison to use the <xref:System.String.Length%2A> property and test for the null string. If targeting .NET Framework 2.0 or later, use the <xref:System.String.IsNullOrEmpty%2A> method.
3841

3942
## When to suppress warnings
40-
It is safe to suppress a warning from this rule if performance is not an issue.
43+
44+
It's safe to suppress a warning from this rule if performance is not an issue.
4145

4246
## Example
43-
The following example illustrates the different techniques that are used to look for an empty string.
4447

45-
[!code-csharp[FxCop.Performance.StringTest#1](../code-quality/codesnippet/CSharp/ca1820-test-for-empty-strings-using-string-length_1.cs)]
48+
The following example illustrates the different techniques that are used to look for an empty string.
49+
50+
[!code-csharp[FxCop.Performance.StringTest#1](../code-quality/codesnippet/CSharp/ca1820-test-for-empty-strings-using-string-length_1.cs)]

docs/cross-platform/develop-apps-for-the-universal-windows-platform-uwp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The Universal Windows Platform is simply a collection of contracts and versions.
3333

3434
- [Windows 10](http://windows.microsoft.com/windows/downloads). Visual Studio 2017 supports UWP development only on Windows 10. For more details, see Visual Studio [Platform targeting](/visualstudio/productinfo/vs2017-compatibility-vs) and [System requirements](/visualstudio/productinfo/vs2017-system-requirements-vs).
3535

36-
- [Visual Studio](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). You will also need the optional Universal Windows Platform development workload.
36+
- [Visual Studio](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017). You will also need the optional Universal Windows Platform development workload.
3737

3838
![UWP workload](media/uwp_workload.png)
3939

docs/cross-platform/unity-scripting-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ With the release of Unity 2017.1, Unity introduced an experimental version of it
1818
## Prerequisites
1919

2020
* [Unity 2017.1 or above](https://unity3d.com/) (2018.2 recommended)
21-
* [Visual Studio 2017](https://visualstudio.microsoft.com/downloads/)
21+
* [Visual Studio 2017](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017)
2222

2323
## Enabling the .NET 4.x scripting runtime in Unity
2424

docs/data-tools/accessing-data-in-visual-studio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In Visual Studio, you can create applications that connect to data in virtually
2222

2323
For applications in JavaScript, Python, PHP, Ruby, or C++, you connect to data like you do anything else, by obtaining libraries and writing code. For .NET applications, Visual Studio provides tools that you can use to explore data sources, create object models to store and manipulate data in memory, and bind data to the user interface. Microsoft Azure provides SDKs for .NET, Java, Node.js, PHP, Python, Ruby, and mobile apps, and tools in Visual Studio for connecting to Azure Storage.
2424

25-
The following lists show just a few of the many database and storage systems that can be used from Visual Studio. The [Microsoft Azure](https://azure.microsoft.com/) offerings are data services that include all provisioning and administration of the underlying data store. The **Azure development** workload in [Visual Studio 2017](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) enables you to work with Azure data stores directly from Visual Studio.
25+
The following lists show just a few of the many database and storage systems that can be used from Visual Studio. The [Microsoft Azure](https://azure.microsoft.com/) offerings are data services that include all provisioning and administration of the underlying data store. The **Azure development** workload in [Visual Studio 2017](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017) enables you to work with Azure data stores directly from Visual Studio.
2626

2727
![Azure development workload](media/azure-development-workload.png)
2828

docs/debugger/debugging-absolute-beginners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Next, we will create an application that has a few bugs.
7272

7373
1. You must have Visual Studio installed and either the **.NET desktop development** workload or the **.NET Core cross platform development** workload installed, depending on which app type you want to create.
7474

75-
If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) page to install it for free.
75+
If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017) page to install it for free.
7676

7777
If you need to install the workload but already have Visual Studio, click **Tools** > **Get Tools and Features**. The Visual Studio Installer launches. Choose the **.NET desktop development** (or **.NET Core cross platform development**) workload, then choose **Modify**.
7878

docs/deployment/deploying-applications-services-and-components.md

Lines changed: 19 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Deployment feature tour"
33
description: "Learn about your options for deploying apps from Visual Studio."
44
ms.custom: "mvc"
5-
ms.date: 06/22/2018
5+
ms.date: 01/29/2019
66
ms.topic: "quickstart"
77
dev_langs:
88
- "FSharp"
@@ -43,20 +43,28 @@ Deployment to a local folder is typically used for testing, or to begin a staged
4343

4444
## Publish to Azure
4545

46-
- **ASP.NET**, **ASP.NET Core**, **Python**, and **Node.js**: You can use the Publish tool to quickly deploy apps to Azure App Service or to an Azure Virtual Machine. In Solution Explorer, right-click the project and choose **Publish**. (If you have previously configured any publishing profiles, you must then click **Create new profile**.) In the Publish dialog box, choose either **App Service** or **Azure Virtual Machines**, and then follow the configuration steps.
46+
- **ASP.NET**, **ASP.NET Core**, **Python**, and **Node.js**: Publish to Azure App Service or Azure App Service Linux (using containers) using one of the following methods.
4747

48-
![Choose Azure App Service](../deployment/media/quickstart-publish-azure.png "Choose Azure App Service")
48+
- For continuous (or automated) deployment of apps, use Azure DevOps with [Azure Pipelines](https://docs.microsoft.com/azure/devops/pipelines/get-started-yaml?view=azdevops).
4949

50-
In Visual Studio 2017 version 15.7 and later, you can deploy ASP.NET Core apps to **App Service for Linux**.
50+
- For one-time (or manual) deployment of apps, use the **Publish** tool in Visual Studio.
5151

52-
For Python apps, also see [Python - Publishing to Azure App Service](../python/publishing-python-web-applications-to-azure-from-visual-studio.md?toc=/visualstudio/deployment/toc.json&bc=/visualstudio/deployment/_breadcrumb/toc.json).
52+
For deployment that provides more customized configuration of the server, you can also use the **Publish** tool to deploy apps to an Azure Virtual Machine.
5353

54-
For a quick introduction, see [Publish to Azure](quickstart-deploy-to-azure.md) and [Publish to Linux](quickstart-deploy-to-linux.md). Also, see [Publish an ASP.NET Core app to Azure](/aspnet/core/tutorials/publish-to-azure-webapp-using-vs). For deployment using Git, see [Continuous deployment of ASP.NET Core to Azure with Git](/aspnet/core/publishing/azure-continuous-deployment).
54+
To use the **Publish** tool, right-click the project in Solution Explorer and choose **Publish**. (If you have previously configured any publishing profiles, you must then click **Create new profile**.) In the Publish dialog box, choose either **App Service** or **Azure Virtual Machines**, and then follow the configuration steps.
5555

56-
For information on importing a publish profile from Azure App Service to Visual Studio, see [Import publish settings and deploy to Azure](../deployment/tutorial-import-publish-settings-azure.md).
56+
![Choose Azure App Service](../deployment/media/quickstart-publish-azure.png "Choose Azure App Service")
5757

58-
> [!NOTE]
59-
> If you do not already have an Azure account, you can [sign up here](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=doc&utm_campaign=visualstudio).
58+
Starting in Visual Studio 2017 version 15.7, you can deploy ASP.NET Core apps to **App Service for Linux**.
59+
60+
For Python apps, also see [Python - Publishing to Azure App Service](../python/publishing-python-web-applications-to-azure-from-visual-studio.md?toc=/visualstudio/deployment/toc.json&bc=/visualstudio/deployment/_breadcrumb/toc.json).
61+
62+
For a quick introduction, see [Publish to Azure](quickstart-deploy-to-azure.md) and [Publish to Linux](quickstart-deploy-to-linux.md). Also, see [Publish an ASP.NET Core app to Azure](/aspnet/core/tutorials/publish-to-azure-webapp-using-vs). For deployment using Git, see [Continuous deployment of ASP.NET Core to Azure with Git](/aspnet/core/publishing/azure-continuous-deployment).
63+
64+
For information on importing a publish profile from Azure App Service to Visual Studio, see [Import publish settings and deploy to Azure](../deployment/tutorial-import-publish-settings-azure.md).
65+
66+
> [!NOTE]
67+
> If you do not already have an Azure account, you can [sign up here](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=doc&utm_campaign=visualstudio).
6068
6169
## Publish to Web or deploy to network share
6270

@@ -106,9 +114,9 @@ If you require more a complex installation of a desktop application than [ClickO
106114

107115
You can enable more sophisticated development and testing by deploying your applications into virtual environments. For more information, see [Test on a lab environment](../test/lab-management/using-a-lab-environment-for-your-application-lifecycle.md).
108116

109-
## DevOps deployment
117+
## Continuous deployment
110118

111-
In a team environment, you can use Azure Pipelines to enable continuous deployment of your app. For more information, see [Azure Pipelines](/azure/devops/pipelines/index?view=vsts) and [Deploy to Azure](/azure/devops/deploy-azure/index?view=vsts).
119+
You can use Azure Pipelines to enable continuous deployment of your app. For more information, see [Azure Pipelines](/azure/devops/pipelines/index?view=vsts) and [Deploy to Azure](/azure/devops/deploy-azure/index?view=vsts).
112120

113121
## Deployment for other app types
114122

docs/deployment/includes/quickstart-prereqs-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
* An Azure subscription. If you do not already have subscription, [sign up for free](https://azure.microsoft.com/free/dotnet/), which includes $200 in credit for 30 days and 12 months of popular free services.
88

9-
* An ASP.NET Core, .NET Core, or Node.js project. If you don't already have a project, select an option below:
9+
* An ASP.NET, ASP.NET Core, .NET Core, or Node.js project. If you don't already have a project, select an option below:
1010
* ASP.NET: Follow [Quickstart: Use Visual Studio to create your first ASP.NET Core web app](../../ide/quickstart-aspnet-core.md), or use **File** > **New Project**, select **Visual C#** > **.NET Core**, then select **ASP.NET Core Web Application**. When prompted, select the **Web Application (Model-View-Controller)** template, make sure that **No Authentication** is selected, and then select **OK**.
1111
* Node.js: Follow [Quickstart: Use Visual Studio to create your first Node.js app](../../ide/quickstart-nodejs.md), or use **File** > **New Project**, select **JavaScript**, then select **Blank Node.js Web Application**.
1212

docs/deployment/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Visual Studio provides several different tools to help you deploy your apps.
7777
<div class="card">
7878
<div class="cardImageOuter">
7979
<div class="cardImage">
80-
<img src="https://docs.microsoft.com/media/common/i_get-started.svg" alt="Deploy to Azure App Service">
80+
<img src="https://docs.microsoft.com/media/logos/logo_azure.svg" alt="Deploy to Azure App Service">
8181
</div>
8282
</div>
8383
<div class="cardText">
@@ -95,7 +95,7 @@ Visual Studio provides several different tools to help you deploy your apps.
9595
<div class="card">
9696
<div class="cardImageOuter">
9797
<div class="cardImage">
98-
<img src="https://docs.microsoft.com/media/common/i_get-started.svg" alt="Deploy to Azure App Service">
98+
<img src="https://docs.microsoft.com/media/logos/logo_azure.svg" alt="Deploy to Azure App Service">
9999
</div>
100100
</div>
101101
<div class="cardText">
@@ -118,7 +118,7 @@ Visual Studio provides several different tools to help you deploy your apps.
118118
<div class="card">
119119
<div class="cardImageOuter">
120120
<div class="cardImage">
121-
<img src="https://docs.microsoft.com/media/logos/logo_net.svg" alt="Deploy ASP.NET to Azure">
121+
<img src="https://docs.microsoft.com/media/logos/logo_azure.svg" alt="Deploy ASP.NET to Azure">
122122
</div>
123123
</div>
124124
<div class="cardText">
@@ -154,7 +154,7 @@ Visual Studio provides several different tools to help you deploy your apps.
154154
<div class="card">
155155
<div class="cardImageOuter">
156156
<div class="cardImage">
157-
<img src="https://docs.microsoft.com/media/logos/logo_net.svg" alt="Deploy a .NET core app">
157+
<img src="https://docs.microsoft.com/media/logos/logo_NETcore.svg" alt="Deploy a .NET core app">
158158
</div>
159159
</div>
160160
<div class="cardText">
@@ -190,7 +190,7 @@ Visual Studio provides several different tools to help you deploy your apps.
190190
<div class="card">
191191
<div class="cardImageOuter">
192192
<div class="cardImage">
193-
<img src="https://docs.microsoft.com/media/logos/logo_net.svg" alt="Import publish settings and deploy to Azure App Service">
193+
<img src="https://docs.microsoft.com/media/logos/logo_azure.svg" alt="Import publish settings and deploy to Azure App Service">
194194
</div>
195195
</div>
196196
<div class="cardText">
@@ -262,7 +262,7 @@ Visual Studio provides several different tools to help you deploy your apps.
262262
<div class="card">
263263
<div class="cardImageOuter">
264264
<div class="cardImage">
265-
<img src="https://docs.microsoft.com/media/common/i_learn-about.svg" alt="Learn about deployment in Visual C++">
265+
<img src="https://docs.microsoft.com/media/logos/logo_Cplusplus.svg" alt="Learn about deployment in Visual C++">
266266
</div>
267267
</div>
268268
<div class="cardText">

docs/deployment/quickstart-deploy-to-a-web-site.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Publish to a website
3-
ms.date: 06/22/2018
3+
ms.date: 01/29/2019
44
ms.topic: "quickstart"
55
helpviewer_keywords:
66
- "deployment, website"
@@ -17,6 +17,9 @@ You can use the **Publish** tool to publish ASP.NET, ASP.NET Core, .NET Core, an
1717

1818
[!INCLUDE [quickstart-prereqs](includes/quickstart-prereqs.md)]
1919

20+
> [!NOTE]
21+
> If you need to publish a Windows desktop application to a network file share, see [Deploy a desktop app using ClickOnce](how-to-publish-a-clickonce-application-using-the-publish-wizard.md) (C# or Visual Basic) or [Deploy a native app using ClickOnce](/cpp/ide/clickonce-deployment-for-visual-cpp-applications) (C++).
22+
2023
## Publish to a Web site
2124

2225
1. In Solution Explorer, right-click the project and choose **Publish** (or use the **Build** > **Publish** menu item).

0 commit comments

Comments
 (0)