From 19bb6652e8b0c2f78b592529db942a9942660c76 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Thu, 21 Jun 2018 11:45:08 -0700 Subject: [PATCH 1/2] Changed visualstudio.com to visualstudio.microsoft.com --- docs/core/additional-tools/index.md | 2 +- docs/core/linux-prerequisites.md | 10 +++++----- docs/core/macos-prerequisites.md | 6 +++--- docs/core/tutorials/using-on-mac-vs-full-solution.md | 2 +- docs/core/tutorials/using-on-mac-vs.md | 2 +- docs/csharp/whats-new/index.md | 8 ++++---- docs/framework/get-started/index.md | 2 +- .../framework/tools/developer-command-prompt-for-vs.md | 2 +- docs/framework/tools/index.md | 2 +- docs/machine-learning/tutorials/sentiment-analysis.md | 2 +- docs/machine-learning/tutorials/taxi-fare.md | 2 +- docs/samples-and-tutorials/index.md | 2 +- docs/standard/clr.md | 2 +- .../visual-studio-tools-for-docker.md | 4 ++-- ...form-development-with-the-portable-class-library.md | 4 ++-- .../docker-app-development-workflow.md | 2 +- .../net-core-container-scenarios.md | 4 ++-- .../modernize-with-azure-and-containers/index.md | 2 +- ...oft-technologies-in-cloud-optimized-applications.md | 4 ++-- docs/standard/tour.md | 2 +- index.md | 2 +- 21 files changed, 34 insertions(+), 34 deletions(-) diff --git a/docs/core/additional-tools/index.md b/docs/core/additional-tools/index.md index 82b6ac5ff7a56..6e71fc3a902f7 100644 --- a/docs/core/additional-tools/index.md +++ b/docs/core/additional-tools/index.md @@ -12,7 +12,7 @@ This section compiles a list of tools that support and extend the .NET Core func ## [WCF Web Service Reference tool](wcf-web-service-reference-guide.md) -The WCF (Windows Communication Foundation) Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/news/releasenotes/vs2017-relnotes#WCFTools). This tool retrieves metadata from a web service in the current solution, on a network location, or from a WSDL file, and generates a source file compatible with .NET Core, defining a WCF proxy class with methods that you can use to access the web service operations. +The WCF (Windows Communication Foundation) Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://visualstudio.microsoft.com/news/releasenotes/vs2017-relnotes#WCFTools). This tool retrieves metadata from a web service in the current solution, on a network location, or from a WSDL file, and generates a source file compatible with .NET Core, defining a WCF proxy class with methods that you can use to access the web service operations. ## [WCF dotnet-svcutil tool](dotnet-svcutil-guide.md) diff --git a/docs/core/linux-prerequisites.md b/docs/core/linux-prerequisites.md index c3bdb1117f96f..728c9ec3e8948 100644 --- a/docs/core/linux-prerequisites.md +++ b/docs/core/linux-prerequisites.md @@ -191,7 +191,7 @@ For Red Hat .NET channel access registration help, see [Chapter 1 of the .NET Co **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://www.visualstudio.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). |Runtimes / SDKs |Ubuntu 18.04 |Ubuntu 17.10 |Ubuntu 16.04 / Linux Mint 18|Ubuntu 14.04 / Linux Mint 17| |---------------------------------|----------------|----------------|----------------------------|----------------------------| @@ -247,7 +247,7 @@ To install .NET Core on supported Debian versions (64 bit): **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://www.visualstudio.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). |Runtimes / SDKs |Debian 9 |Debian 8 | |---------------------------------|---------------|---------------| @@ -300,7 +300,7 @@ To install .NET Core on supported Fedora versions: **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://www.visualstudio.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). |Runtimes / SDKs |Fedora 27 |Fedora 26 | |---------------------------------|-------------------|----------------------| @@ -357,7 +357,7 @@ To install .NET Core for supported CentOS and Oracle Linux distributions/version **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://www.visualstudio.com/vs/preview/). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview/). * .NET Core Runtime 2.1.0 [install link](https://www.microsoft.com/net/download/linux-package-manager/centos/runtime-2.1.0) * .NET Core SDK 2.1.300 [install link](https://www.microsoft.com/net/download/linux-package-manager/centos/sdk-2.1.300) @@ -417,7 +417,7 @@ To install .NET Core 2.x for supported SUSE Linux Enterprise Server and OpenSUSE **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://www.visualstudio.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). **SUSE Linux Enterprise Server** diff --git a/docs/core/macos-prerequisites.md b/docs/core/macos-prerequisites.md index ec763abae1be9..da800984f3470 100644 --- a/docs/core/macos-prerequisites.md +++ b/docs/core/macos-prerequisites.md @@ -7,7 +7,7 @@ ms.date: 09/27/2017 --- # Prerequisites for .NET Core on macOS -This article shows you the supported macOS versions and .NET Core dependencies that you need to develop, deploy, and run .NET Core applications on macOS machines. The supported OS versions and dependencies that follow apply to the three ways of developing .NET Core apps on a Mac: via the [command-line with your favorite editor](tutorials/using-with-xplat-cli.md), [Visual Studio Code](https://code.visualstudio.com/), and [Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/). +This article shows you the supported macOS versions and .NET Core dependencies that you need to develop, deploy, and run .NET Core applications on macOS machines. The supported OS versions and dependencies that follow apply to the three ways of developing .NET Core apps on a Mac: via the [command-line with your favorite editor](tutorials/using-with-xplat-cli.md), [Visual Studio Code](https://code.visualstudio.com/), and [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/). ## Supported macOS versions @@ -96,11 +96,11 @@ echo 'ulimit -n 2048' | sudo tee -a /etc/profile ## Visual Studio for Mac -You can use any editor to develop .NET Core applications using the .NET Core SDK. However, if you want to develop .NET Core applications on a Mac in an integrated development environment, you can use [Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/). +You can use any editor to develop .NET Core applications using the .NET Core SDK. However, if you want to develop .NET Core applications on a Mac in an integrated development environment, you can use [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/). .NET Core development on macOS with Visual Studio for Mac requires: * A supported version of the macOS operating system * OpenSSL (.NET Core 1.x only; .NET Core 2.x uses security services available natively in macOS) * .NET Core SDK for Mac -* [Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/) +* [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/) diff --git a/docs/core/tutorials/using-on-mac-vs-full-solution.md b/docs/core/tutorials/using-on-mac-vs-full-solution.md index 8ae0f1d1e2637..71e6d282b30d1 100644 --- a/docs/core/tutorials/using-on-mac-vs-full-solution.md +++ b/docs/core/tutorials/using-on-mac-vs-full-solution.md @@ -20,7 +20,7 @@ This tutorial shows you how to create an application that accepts a search word - OpenSSL (if running .NET Core 1.1): See the [Prerequisites for .NET Core on Mac](../macos-prerequisites.md) topic. - [.NET Core SDK 1.1 or later](https://www.microsoft.com/net/core#macos) -- [Visual Studio 2017 for Mac](https://www.visualstudio.com/vs/visual-studio-mac/) +- [Visual Studio 2017 for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/) For more information on prerequisites, see the [Prerequisites for .NET Core on Mac](../../core/macos-prerequisites.md). For the full system requirements of Visual Studio 2017 for Mac, see [Visual Studio 2017 for Mac Product Family System Requirements](/visualstudio/productinfo/vs2017-system-requirements-mac). diff --git a/docs/core/tutorials/using-on-mac-vs.md b/docs/core/tutorials/using-on-mac-vs.md index aff5d9bffcdd3..9805c2aa36199 100644 --- a/docs/core/tutorials/using-on-mac-vs.md +++ b/docs/core/tutorials/using-on-mac-vs.md @@ -22,7 +22,7 @@ See the [Prerequisites for .NET Core on Mac](../../core/macos-prerequisites.md) If you've already installed the prerequisites and Visual Studio for Mac, skip this section and proceed to [Creating a project](#creating-a-project). Follow these steps to install the prerequisites and Visual Studio for Mac: -Download the [Visual Studio for Mac installer](https://www.visualstudio.com/vs/visual-studio-mac/). Run the installer. Read and accept the license agreement. During the install, you're provided the opportunity to install Xamarin, a cross-platform mobile app development technology. Installing Xamarin and its related components is optional for .NET Core development. For a walk-through of the Visual Studio for Mac install process, see [Introducing Visual Studio for Mac](https://developer.xamarin.com/guides/cross-platform/visual-studio-mac/). When the install is complete, start the Visual Studio for Mac IDE. +Download the [Visual Studio for Mac installer](https://visualstudio.microsoft.com/vs/visual-studio-mac/). Run the installer. Read and accept the license agreement. During the install, you're provided the opportunity to install Xamarin, a cross-platform mobile app development technology. Installing Xamarin and its related components is optional for .NET Core development. For a walk-through of the Visual Studio for Mac install process, see [Introducing Visual Studio for Mac](https://developer.xamarin.com/guides/cross-platform/visual-studio-mac/). When the install is complete, start the Visual Studio for Mac IDE. ## Creating a project diff --git a/docs/csharp/whats-new/index.md b/docs/csharp/whats-new/index.md index f8e5f97e482e9..3b5d7c70bd7a9 100644 --- a/docs/csharp/whats-new/index.md +++ b/docs/csharp/whats-new/index.md @@ -17,13 +17,13 @@ major features added in each release. To use the latest features in a point release, you need to [configure the compiler language version](../language-reference/configure-language-version.md) and select the version. * [C# 7.3](csharp-7-3.md): - - This page describes the latest features in the C# language. C# 7.3 is currently available in [Visual Studio 2017 version 15.7](https://www.visualstudio.com/vs/whatsnew/), and in the [.NET Core 2.1 SDK 2.1.300 RC1](../../core/whats-new/index.md). + - This page describes the latest features in the C# language. C# 7.3 is currently available in [Visual Studio 2017 version 15.7](https://visualstudio.microsoft.com/vs/whatsnew/), and in the [.NET Core 2.1 SDK 2.1.300 RC1](../../core/whats-new/index.md). * [C# 7.2](csharp-7-2.md): - - This page describes the features added in the C# language. C# 7.2 is currently available in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/vs/whatsnew/), and in the [.NET Core 2.0 SDK](../../core/whats-new/index.md). + - This page describes the features added in the C# language. C# 7.2 is currently available in [Visual Studio 2017 version 15.5](https://visualstudio.microsoft.com/vs/whatsnew/), and in the [.NET Core 2.0 SDK](../../core/whats-new/index.md). * [C# 7.1](csharp-7-1.md): - - This page describes the features added in C# 7.1. These features were added in [Visual Studio 2017 version 15.3](https://www.visualstudio.com/vs/whatsnew/), and in the [.NET Core 2.0 SDK](../../core/whats-new/index.md). + - This page describes the features added in C# 7.1. These features were added in [Visual Studio 2017 version 15.3](https://visualstudio.microsoft.com/vs/whatsnew/), and in the [.NET Core 2.0 SDK](../../core/whats-new/index.md). * [C# 7.0](csharp-7.md): - - This page describes the features added in C# 7.0. These features were added in [Visual Studio 2017](https://www.visualstudio.com/vs/whatsnew/) and [.NET Core 1.0](../../core/whats-new/index.md) and later + - This page describes the features added in C# 7.0. These features were added in [Visual Studio 2017](https://visualstudio.microsoft.com/vs/whatsnew/) and [.NET Core 1.0](../../core/whats-new/index.md) and later * [C# 6](csharp-6.md): - This page describes the features that were added in C# 6. These features are available in Visual Studio 2015 for Windows developers, and on .NET Core 1.0 for developers exploring C# on macOS and Linux. * [Cross Platform Support](../../core/index.md): diff --git a/docs/framework/get-started/index.md b/docs/framework/get-started/index.md index a55c3c2b673f8..15b19c9307d48 100644 --- a/docs/framework/get-started/index.md +++ b/docs/framework/get-started/index.md @@ -66,7 +66,7 @@ To develop .NET Framework apps or components, do the following: 2. Select the language or languages supported by the .NET Framework that you intend to use to develop your apps. A number of languages are available, including [Visual Basic](../../visual-basic/index.md), [C#](../../csharp/index.md), [F#](../../fsharp/index.md), and C++/CLI from Microsoft. (A programming language that allows you to develop apps for the .NET Framework adheres to the [Common Language Infrastructure (CLI) specification](http://go.microsoft.com/fwlink/?LinkId=199862).) -3. Select and install the development environment to use to create your apps and that supports your selected programming language or languages. The Microsoft integrated development environment (IDE) for .NET Framework apps is [Visual Studio](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). It's available in a number of editions. +3. Select and install the development environment to use to create your apps and that supports your selected programming language or languages. The Microsoft integrated development environment (IDE) for .NET Framework apps is [Visual Studio](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). It's available in a number of editions. For more information on developing apps that target the .NET Framework, see the [Development Guide](../../../docs/framework/development-guide.md). diff --git a/docs/framework/tools/developer-command-prompt-for-vs.md b/docs/framework/tools/developer-command-prompt-for-vs.md index 3f470803015b1..bace71c1a1c06 100644 --- a/docs/framework/tools/developer-command-prompt-for-vs.md +++ b/docs/framework/tools/developer-command-prompt-for-vs.md @@ -18,7 +18,7 @@ ms.author: "mairaw" The Developer Command Prompt for Visual Studio automatically sets the environment variables that enable you to easily use .NET Framework tools. The Developer Command Prompt is installed with full or community editions of Visual Studio. It isn't installed with the Express versions of Visual Studio. > [!div class="button"] -[Download Visual Studio](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) +[Download Visual Studio](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) ## Searching for the Command Prompt on your machine diff --git a/docs/framework/tools/index.md b/docs/framework/tools/index.md index 8c1ec7a47a2c1..61199393450fa 100644 --- a/docs/framework/tools/index.md +++ b/docs/framework/tools/index.md @@ -13,7 +13,7 @@ ms.author: "mairaw" # .NET Framework Tools The .NET Framework tools make it easier for you to create, deploy, and manage applications and components that target the .NET Framework. -Most of the .NET Framework tools described in this section are automatically installed with Visual Studio. To download Visual Studio, visit the [Visual Studio Downloads](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) page. +Most of the .NET Framework tools described in this section are automatically installed with Visual Studio. To download Visual Studio, visit 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. You can run all the tools from the command line with the exception of the Assembly Cache Viewer (Shfusion.dll). You must access Shfusion.dll from File Explorer. diff --git a/docs/machine-learning/tutorials/sentiment-analysis.md b/docs/machine-learning/tutorials/sentiment-analysis.md index f3accadd439e3..11759d4a44f11 100644 --- a/docs/machine-learning/tutorials/sentiment-analysis.md +++ b/docs/machine-learning/tutorials/sentiment-analysis.md @@ -30,7 +30,7 @@ The sample is a console app that uses ML.NET to train a model that classifies an ## Prerequisites -* [Visual Studio 2017 15.6 or later](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) with the ".NET Core cross-platform development" workload installed. +* [Visual Studio 2017 15.6 or later](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) with the ".NET Core cross-platform development" workload installed. * The [Wikipedia detox line data tab separated file (wikiPedia-detox-250-line-data.tsv)](https://github.com/dotnet/machinelearning/blob/master/test/data/wikipedia-detox-250-line-data.tsv). * The [Wikipedia detox line test tab separated file (wikipedia-detox-250-line-test.tsv)](https://github.com/dotnet/machinelearning/blob/master/test/data/wikipedia-detox-250-line-test.tsv). diff --git a/docs/machine-learning/tutorials/taxi-fare.md b/docs/machine-learning/tutorials/taxi-fare.md index d3f10546e0bbf..3bc89b37a9507 100644 --- a/docs/machine-learning/tutorials/taxi-fare.md +++ b/docs/machine-learning/tutorials/taxi-fare.md @@ -29,7 +29,7 @@ In this tutorial, you learn how to: ## Prerequisites -* [Visual Studio 2017 15.6 or later](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) with the ".NET Core cross-platform development" workload installed. +* [Visual Studio 2017 15.6 or later](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) with the ".NET Core cross-platform development" workload installed. ## Understand the problem diff --git a/docs/samples-and-tutorials/index.md b/docs/samples-and-tutorials/index.md index ab2ce4ae01d1e..854f4c104fb6f 100644 --- a/docs/samples-and-tutorials/index.md +++ b/docs/samples-and-tutorials/index.md @@ -108,6 +108,6 @@ Many topics show source code and samples that are available for viewing or downl 1. Navigate within the repository's folders to the sample's location. The relative path to the sample's location appears in your browser's address bar when you follow the link to the sample. 1. To run a sample, you have several options: * Use the [dotnet CLI tools](../core/tools/index.md): In a console window, navigate to the sample's folder and use dotnet CLI commands. - * Use [Visual Studio](https://www.visualstudio.com/) or [Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/): Open the sample by selecting **File > Open > Project/Solution** from the menu bar, navigate to the sample project folder, and select the project file (*.csproj* or *.fsproj*). + * Use [Visual Studio](https://visualstudio.microsoft.com/) or [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/): Open the sample by selecting **File > Open > Project/Solution** from the menu bar, navigate to the sample project folder, and select the project file (*.csproj* or *.fsproj*). * Use [Visual Studio Code](https://code.visualstudio.com/): Open the sample by selecting **File > Open Folder** from the menu bar and selecting the sample's project folder. * Use a different IDE that supports .NET Core projects. diff --git a/docs/standard/clr.md b/docs/standard/clr.md index 814ae91124e35..71cf19380a364 100644 --- a/docs/standard/clr.md +++ b/docs/standard/clr.md @@ -26,7 +26,7 @@ The .NET Framework provides a run-time environment called the common language ru Compilers and tools expose the common language runtime's functionality and enable you to write code that benefits from this managed execution environment. Code that you develop with a language compiler that targets the runtime is called managed code; it benefits from features such as cross-language integration, cross-language exception handling, enhanced security, versioning and deployment support, a simplified model for component interaction, and debugging and profiling services. > [!NOTE] -> Compilers and tools are able to produce output that the common language runtime can consume because the type system, the format of metadata, and the runtime environment (the virtual execution system) are all defined by a public standard, the ECMA Common Language Infrastructure specification. For more information, see [ECMA C# and Common Language Infrastructure Specifications](https://www.visualstudio.com/license-terms/ecma-c-common-language-infrastructure-standards/). +> Compilers and tools are able to produce output that the common language runtime can consume because the type system, the format of metadata, and the runtime environment (the virtual execution system) are all defined by a public standard, the ECMA Common Language Infrastructure specification. For more information, see [ECMA C# and Common Language Infrastructure Specifications](https://visualstudio.microsoft.com/license-terms/ecma-c-common-language-infrastructure-standards/). To enable the runtime to provide services to managed code, language compilers must emit metadata that describes the types, members, and references in your code. Metadata is stored with the code; every loadable common language runtime portable executable (PE) file contains metadata. The runtime uses metadata to locate and load classes, lay out instances in memory, resolve method invocations, generate native code, enforce security, and set run-time context boundaries. diff --git a/docs/standard/containerized-lifecycle-architecture/design-develop-containerized-apps/visual-studio-tools-for-docker.md b/docs/standard/containerized-lifecycle-architecture/design-develop-containerized-apps/visual-studio-tools-for-docker.md index b2ea7ab58eebd..088ca9eb0fb88 100644 --- a/docs/standard/containerized-lifecycle-architecture/design-develop-containerized-apps/visual-studio-tools-for-docker.md +++ b/docs/standard/containerized-lifecycle-architecture/design-develop-containerized-apps/visual-studio-tools-for-docker.md @@ -17,8 +17,8 @@ With the latest versions of Docker for Windows, it is easier than ever to develo If you're using Visual Studio 2015, you must have Update 3 or a later version plus the Visual Studio Tools for Docker. -**More info:** For instructions on installing Visual Studio, go to [https://www.visualstudio.com/\ -products/vs-2015-product-editions](https://www.visualstudio.com/products/vs-2015-product-editions). +**More info:** For instructions on installing Visual Studio, go to [https://visualstudio.microsoft.com/\ +products/vs-2015-product-editions](https://visualstudio.microsoft.com/products/vs-2015-product-editions). To see more about installing Visual Studio Tools for Docker, go to and . diff --git a/docs/standard/cross-platform/cross-platform-development-with-the-portable-class-library.md b/docs/standard/cross-platform/cross-platform-development-with-the-portable-class-library.md index d8ec37095dbc7..3aa6a3ce5dc45 100644 --- a/docs/standard/cross-platform/cross-platform-development-with-the-portable-class-library.md +++ b/docs/standard/cross-platform/cross-platform-development-with-the-portable-class-library.md @@ -45,8 +45,8 @@ The .NET Framework Portable Class Library project type in Visual Studio helps yo |Visual Studio Express 2010 versions|No.| |Visual Studio 2012 Professional, Premium, or Ultimate|Yes. For Windows Phone 8.0 support, install the [Windows Phone SDK 8.0](https://www.microsoft.com/download/details.aspx?id=35471).| |Visual Studio Express 2012 versions|No.| -|Visual Studio 2013 Professional, Premium, or Ultimate|Yes. For Windows Phone 8.1 support, install the [latest version of Visual Studio 2013](https://www.visualstudio.com/vs/older-downloads/).| -|Visual Studio Community 2013 for Windows|Yes, when you install the [latest version of Visual Studio Community 2013](https://www.visualstudio.com/vs/older-downloads/), which includes Update 2.| +|Visual Studio 2013 Professional, Premium, or Ultimate|Yes. For Windows Phone 8.1 support, install the [latest version of Visual Studio 2013](https://visualstudio.microsoft.com/vs/older-downloads/).| +|Visual Studio Community 2013 for Windows|Yes, when you install the [latest version of Visual Studio Community 2013](https://visualstudio.microsoft.com/vs/older-downloads/), which includes Update 2.| ## Creating a Portable Class Library project diff --git a/docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md b/docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md index 2c1fcfedc87c0..e03721e0404dd 100644 --- a/docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md +++ b/docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md @@ -61,7 +61,7 @@ You can start coding your application in plain .NET (usually in .NET Core if you [*https://docs.docker.com/docker-for-windows/*](https://docs.docker.com/docker-for-windows/) - **Visual Studio 2017** - [*https://www.visualstudio.com/downloads/*](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs) + [*https://visualstudio.microsoft.com/downloads/*](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs) ![](./media/image4.png) diff --git a/docs/standard/microservices-architecture/net-core-net-framework-containers/net-core-container-scenarios.md b/docs/standard/microservices-architecture/net-core-net-framework-containers/net-core-container-scenarios.md index cd79649b6c8e3..bcd04412a50d6 100644 --- a/docs/standard/microservices-architecture/net-core-net-framework-containers/net-core-container-scenarios.md +++ b/docs/standard/microservices-architecture/net-core-net-framework-containers/net-core-container-scenarios.md @@ -19,9 +19,9 @@ Clearly, if your goal is to have an application (web application or service) tha .NET Core also supports macOS as a development platform. However, when you deploy containers to a Docker host, that host must (currently) be based on Linux or Windows. For example, in a development environment, you could use a Linux VM running on a Mac. -[Visual Studio](https://www.visualstudio.com/) provides an integrated development environment (IDE) for Windows and supports Docker development. +[Visual Studio](https://visualstudio.microsoft.com/) provides an integrated development environment (IDE) for Windows and supports Docker development. -[Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/) is an IDE, evolution of Xamarin Studio, running in macOS and supports Docker since mid-2017. +[Visual Studio for Mac](https://visualstudio.microsoft.com/vs/visual-studio-mac/) is an IDE, evolution of Xamarin Studio, running in macOS and supports Docker since mid-2017. You can also use [Visual Studio Code](https://code.visualstudio.com/) (VS Code) on macOS, Linux, and Windows. VS Code fully supports .NET Core, including IntelliSense and debugging. Because VS Code is a lightweight editor, you can use it to develop containerized apps on the Mac in conjunction with the Docker CLI and the [.NET Core command-line interface (CLI) tools](../../../core/tools/index.md). You can also target .NET Core with most third-party editors like Sublime Text, Emacs, vi, and the open-source OmniSharp project, which provides IntelliSense support for .NET languages. In addition to the IDEs and editors, you can use the .NET Core CLI for all supported platforms. diff --git a/docs/standard/modernize-with-azure-and-containers/index.md b/docs/standard/modernize-with-azure-and-containers/index.md index 0369efce1bf54..0b5bd2ce333e1 100644 --- a/docs/standard/modernize-with-azure-and-containers/index.md +++ b/docs/standard/modernize-with-azure-and-containers/index.md @@ -117,7 +117,7 @@ Each maturity level in the modernization process is associated with the followin - **Cloud-Optimized** (Managed Services and Windows Containers): This model is about making a few important deployment optimizations to gain some significant benefits from the cloud, without changing the core architecture of the application. The fundamental step here is to add [Windows Containers](https://docs.microsoft.com/virtualization/windowscontainers/about/) support to your existing .NET Framework applications. This important step (containerization) doesn't require touching the code, so the overall lift and shift effort is light. You can use tools like [Image2Docker](https://github.com/docker/communitytools-image2docker-win) or Visual Studio, with its tools for [Docker](https://www.docker.com/). Visual Studio automatically chooses smart defaults for ASP.NET applications and Windows Containers images. These tools offer both a rapid inner loop, and a fast path to get the containers to Azure. Your agility is improved when you deploy to multiple environments. Then, moving to production, you can deploy your Windows Containers to [Azure Web App for Containers](https://azure.microsoft.com/en-us/services/app-service/containers/), [Azure Container Instances (ACI), and Azure VMs with Windows Server 2016 and containers if you prefer an IaaS approach. For slightly more complex multi-container applications, into orchestrators like [Azure Service Fabric](https://azure.microsoft.com/services/service-fabric/) or [Azure Kubernetes Service (AKS/ACS)](https://azure.microsoft.com/en-us/services/container-service/). -During this initial modernization, you can also add assets from the cloud, such as monitoring with tools like [Azure Application Insights](https://docs.microsoft.com/azure/application-insights/app-insights-overview); CI/CD pipelines for your app lifecycles with [Visual Studio Team Services](https://www.visualstudio.com/team-services/); and many more data resource services that are available in Azure. For instance, you can modify a monolithic web app that was originally developed by using traditional [ASP.NET Web Forms](https://www.asp.net/web-forms) or [ASP.NET MVC](https://www.asp.net/mvc), but now you deploy it by using Windows Containers. When you use Windows Containers, you should also migrate your data to a database in [Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/sql-database/), all without changing the core architecture of your application. +During this initial modernization, you can also add assets from the cloud, such as monitoring with tools like [Azure Application Insights](https://docs.microsoft.com/azure/application-insights/app-insights-overview); CI/CD pipelines for your app lifecycles with [Visual Studio Team Services](https://visualstudio.microsoft.com/team-services/); and many more data resource services that are available in Azure. For instance, you can modify a monolithic web app that was originally developed by using traditional [ASP.NET Web Forms](https://www.asp.net/web-forms) or [ASP.NET MVC](https://www.asp.net/mvc), but now you deploy it by using Windows Containers. When you use Windows Containers, you should also migrate your data to a database in [Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/sql-database/), all without changing the core architecture of your application. - **Cloud-Native**: As introduced, you should think about architecting [cloud-native](https://www.gartner.com/doc/3181919/architect-design-cloudnative-applications) applications when you are targeting large and complex applications with multiple independent development teams working on different microservices that can be developed and deployed autonomously. Also, due to granularized and independent scalability per microservice. These architectural approaches face very important challenges and complexities but can be greatly simplified by using cloud PaaS and orchestrators like [Azure Kubernetes Service (AKS/ACS)](https://azure.microsoft.com/en-us/services/container-service/) (managed Kubernetes), [Azure Service Fabric, and [Azure Functions](https://azure.microsoft.com/services/functions/) for a serverless approach. All these approaches (like microservices and Serverless) typically require you to architect for the cloud and write new code—code that is adapted to specific PaaS platforms, or code that aligns with specific architectures, like microservices. diff --git a/docs/standard/modernize-with-azure-and-containers/modernize-existing-apps-to-cloud-optimized/microsoft-technologies-in-cloud-optimized-applications.md b/docs/standard/modernize-with-azure-and-containers/modernize-existing-apps-to-cloud-optimized/microsoft-technologies-in-cloud-optimized-applications.md index 0bc81832fb3de..bdab431fbdbcb 100644 --- a/docs/standard/modernize-with-azure-and-containers/modernize-existing-apps-to-cloud-optimized/microsoft-technologies-in-cloud-optimized-applications.md +++ b/docs/standard/modernize-with-azure-and-containers/modernize-existing-apps-to-cloud-optimized/microsoft-technologies-in-cloud-optimized-applications.md @@ -19,9 +19,9 @@ The following list describes the tools, technologies, and solutions that are rec - **Monitoring, telemetry, logging, and auditing**: The ability to monitor and audit applications and containers that are running in the cloud is critical for any Cloud-Optimized application. [Azure Application Insights](https://azure.microsoft.com/services/application-insights/) and [Microsoft Operations Management Suite](https://www.microsoft.com/cloud-platform/operations-management-suite) are the main Microsoft tools that provide monitoring and auditing for Cloud-Optimized apps. -- **Provisioning**: Automation tools help you provision the infrastructure and deploy an application to multiple environments (production, testing, staging). You can use tools like Chef and Puppet to manage an application's configuration and environment. This layer also can be implemented by using simpler and more direct approaches. For example, you can deploy directly by using Azure command-line interface (Azure CLI) tooling, and then use the continuous deployment and release management pipelines in [Visual Studio Team Services](https://www.visualstudio.com/team-services/). +- **Provisioning**: Automation tools help you provision the infrastructure and deploy an application to multiple environments (production, testing, staging). You can use tools like Chef and Puppet to manage an application's configuration and environment. This layer also can be implemented by using simpler and more direct approaches. For example, you can deploy directly by using Azure command-line interface (Azure CLI) tooling, and then use the continuous deployment and release management pipelines in [Visual Studio Team Services](https://visualstudio.microsoft.com/team-services/). -- **Application lifecycle**: [Visual Studio Team Services](https://www.visualstudio.com/team-services/) and other tools, like Jenkins, are built automation servers that help you implement CI/CD pipelines, including release management. +- **Application lifecycle**: [Visual Studio Team Services](https://visualstudio.microsoft.com/team-services/) and other tools, like Jenkins, are built automation servers that help you implement CI/CD pipelines, including release management. The next sections of this chapter, and the related walkthroughs, focus specifically on details about the runtime layer (Windows Containers). The guidance describes the ways you can deploy Windows Containers on Windows Server 2016 (and later versions) VMs and Azure Container Instances. It also covers more advanced PaaS platforms like Azure App Service and orchestrator like Azure Service Fabric and Azure Kubernetes Service. diff --git a/docs/standard/tour.md b/docs/standard/tour.md index b94beeda908ff..d1f4803c21105 100644 --- a/docs/standard/tour.md +++ b/docs/standard/tour.md @@ -19,7 +19,7 @@ To learn how to set up a development environment to run the code samples, see th ## Programming languages -.NET supports multiple programming languages. The .NET implementations implement the [Common Language Infrastructure (CLI)](https://www.visualstudio.com/license-terms/ecma-c-common-language-infrastructure-standards/), which among other things specifies a language-independent runtime and language interoperability. This means that you choose any .NET language to build apps and services on .NET. +.NET supports multiple programming languages. The .NET implementations implement the [Common Language Infrastructure (CLI)](https://visualstudio.microsoft.com/license-terms/ecma-c-common-language-infrastructure-standards/), which among other things specifies a language-independent runtime and language interoperability. This means that you choose any .NET language to build apps and services on .NET. Microsoft actively develops and supports three .NET languages: C#, F#, and Visual Basic (VB). diff --git a/index.md b/index.md index a2a8a03de3d5c..5857042652b98 100644 --- a/index.md +++ b/index.md @@ -584,7 +584,7 @@ ms.custom: "updateeachrelease"
- +

Game Development with Visual Studio

Write and debug your games using your game engine of choice with Visual Studio. From 0bab7e2b93ff946700ee913b4f4eff549ed96c49 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Thu, 21 Jun 2018 13:54:04 -0700 Subject: [PATCH 2/2] Changed preview to release link --- docs/core/linux-prerequisites.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/core/linux-prerequisites.md b/docs/core/linux-prerequisites.md index 728c9ec3e8948..4298c2464342d 100644 --- a/docs/core/linux-prerequisites.md +++ b/docs/core/linux-prerequisites.md @@ -191,7 +191,7 @@ For Red Hat .NET channel access registration help, see [Chapter 1 of the .NET Co **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 or newer](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). |Runtimes / SDKs |Ubuntu 18.04 |Ubuntu 17.10 |Ubuntu 16.04 / Linux Mint 18|Ubuntu 14.04 / Linux Mint 17| |---------------------------------|----------------|----------------|----------------------------|----------------------------| @@ -247,7 +247,7 @@ To install .NET Core on supported Debian versions (64 bit): **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 or newer](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). |Runtimes / SDKs |Debian 9 |Debian 8 | |---------------------------------|---------------|---------------| @@ -300,7 +300,7 @@ To install .NET Core on supported Fedora versions: **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 or newer](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). |Runtimes / SDKs |Fedora 27 |Fedora 26 | |---------------------------------|-------------------|----------------------| @@ -357,7 +357,7 @@ To install .NET Core for supported CentOS and Oracle Linux distributions/version **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview/). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 or newer](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). * .NET Core Runtime 2.1.0 [install link](https://www.microsoft.com/net/download/linux-package-manager/centos/runtime-2.1.0) * .NET Core SDK 2.1.300 [install link](https://www.microsoft.com/net/download/linux-package-manager/centos/sdk-2.1.300) @@ -417,7 +417,7 @@ To install .NET Core 2.x for supported SUSE Linux Enterprise Server and OpenSUSE **.NET Core 2.1** >[!IMPORTANT] -> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 Preview 1 or newer](https://visualstudio.microsoft.com/vs/preview). +> To use .NET Core 2.1 with Visual Studio, you need to [install Visual Studio 2017 15.7 or newer](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). **SUSE Linux Enterprise Server**