Skip to content

Commit 38ceb66

Browse files
BillWagnergewarren
andauthored
Remove references to VS for Mac (#42845)
* Remove references to VS for Mac VS for Mac is out of support. Remove references to it. * Remove visual studio for mac tutorials. This should fix the build warnings * Apply suggestions from code review Co-authored-by: Genevieve Warren <[email protected]> --------- Co-authored-by: Genevieve Warren <[email protected]>
1 parent 747860e commit 38ceb66

File tree

33 files changed

+36
-891
lines changed

33 files changed

+36
-891
lines changed

.openpublishing.redirection.core.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1267,6 +1267,26 @@
12671267
"source_path_from_root": "/docs/core/tutorials/vb-with-visual-studio.md",
12681268
"redirect_url": "/dotnet/core/tutorials/with-visual-studio"
12691269
},
1270+
{
1271+
"source_path_from_root": "/docs/core/tutorials/debugging-with-visual-studio-mac.md",
1272+
"redirect_url": "/dotnet/core/tutorials/debugging-with-visual-studio-code"
1273+
},
1274+
{
1275+
"source_path_from_root": "/docs/core/tutorials/library-with-visual-studio-mac.md",
1276+
"redirect_url": "/dotnet/core/tutorials/library-with-visual-studio-code"
1277+
},
1278+
{
1279+
"source_path_from_root": "/docs/core/tutorials/publishing-with-visual-studio-mac.md",
1280+
"redirect_url": "/dotnet/core/tutorials/publishing-with-visual-studio-code"
1281+
},
1282+
{
1283+
"source_path_from_root": "/docs/core/tutorials/testing-library-with-visual-studio-mac.md",
1284+
"redirect_url": "/dotnet/core/tutorials/testing-library-with-visual-studio-code"
1285+
},
1286+
{
1287+
"source_path_from_root": "/docs/core/tutorials/with-visual-studio-mac.md",
1288+
"redirect_url": "/dotnet/core/tutorials/with-visual-studio-code"
1289+
},
12701290
{
12711291
"source_path_from_root": "/docs/core/versions/install-management.md",
12721292
"redirect_url": "/dotnet/core/install/remove-runtime-sdk-versions"

.openpublishing.redirection.fsharp.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@
88
"source_path_from_root": "/docs/fsharp/getting-started-netcore.md",
99
"redirect_url": "/dotnet/fsharp/get-started/get-started-command-line"
1010
},
11+
{
12+
"source_path_from_root": "/docs/fsharp/get-started/get-started-with-visual-studio-for-mac.md",
13+
"redirect_url": "/dotnet/fsharp/get-started/get-started-vscode"
14+
},
1115
{
1216
"source_path_from_root": "/docs/fsharp/introduction-to-functional-programming/first-class-functions.md",
1317
"redirect_url": "/dotnet/fsharp/tutorials/using-functions"

docs/architecture/microservices/docker-application-development-process/index.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Development process for Docker-based applications
3-
description: Get a high-level overview of the options for developing Docker-based applications. Using your choice of Visual Studio for Windows, Visual Studio for Mac, or Visual Studio Code for multiplatform support (Windows, macOS, and Linux).
3+
description: Get a high-level overview of the options for developing Docker-based applications. Using your choice of Visual Studio for Windows or Visual Studio Code for multiplatform support (Windows, macOS, and Linux).
44
ms.date: 11/19/2021
55
---
66
# Development process for Docker-based applications
@@ -17,8 +17,6 @@ Whether you prefer a full and powerful IDE or a lightweight and agile editor, Mi
1717

1818
**Visual Studio (for Windows).** Docker-based .NET 8 application development with Visual Studio requires Visual Studio 2022 version 17.0 or later. Visual Studio 2022 comes with tools for Docker already built in. The tools for Docker let you develop, run, and validate your applications directly in the target Docker environment. You can press <kbd>F5</kbd> to run and debug your application (single container or multiple containers) directly into a Docker host, or press <kbd>CTRL</kbd> + <kbd>F5</kbd> to edit and refresh your application without having to rebuild the container. This IDE is the most powerful development choice for Docker-based apps.
1919

20-
**Visual Studio for Mac.** It's an IDE, evolution of Xamarin Studio, running in macOS. This tool should be the preferred choice for developers working in macOS machines who also want to use a powerful IDE.
21-
2220
**Visual Studio Code and Docker CLI**. If you prefer a lightweight and cross-platform editor that supports any development language, you can use Visual Studio Code and the Docker CLI. This IDE is a cross-platform development approach for macOS, Linux, and Windows. Additionally, Visual Studio Code supports extensions for Docker such as IntelliSense for Dockerfiles and shortcut tasks to run Docker commands from the editor.
2321

2422
By installing [Docker Desktop](https://hub.docker.com/search/?type=edition&offering=community), you can use a single Docker CLI to build apps for both Windows and Linux.

docs/architecture/microservices/net-core-net-framework-containers/net-core-container-scenarios.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,6 @@ Clearly, if your goal is to have an application (web app or service) that can ru
2121

2222
[Visual Studio](https://www.visualstudio.com/vs/) provides an integrated development environment (IDE) for Windows and supports Docker development.
2323

24-
[Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/) is an IDE, evolution of Xamarin Studio, that runs on macOS and supports Docker-based application development. This tool should be the preferred choice for developers working in Mac machines who also want to use a powerful IDE.
25-
2624
You can also use [Visual Studio Code](https://code.visualstudio.com/) on macOS, Linux, and Windows. Visual Studio Code fully supports .NET 8, including IntelliSense and debugging. Because VS Code is a lightweight editor, you can use it to develop containerized apps on the machine in conjunction with the Docker CLI and the [.NET CLI](../../../core/tools/index.md). You can also target .NET 8 with most third-party editors like Sublime, Emacs, vi, and the open-source OmniSharp project, which also provides IntelliSense support.
2725

2826
In addition to the IDEs and editors, you can use the [.NET CLI](../../../core/tools/index.md) for all supported platforms.

docs/core/deploying/single-file/overview.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -108,10 +108,6 @@ Visual Studio creates reusable publishing profiles that control how your applica
108108

109109
For more information, see [Publish .NET Core apps with Visual Studio](../deploy-with-vs.md).
110110

111-
# [Visual Studio for Mac](#tab/vsmac)
112-
113-
Visual Studio for Mac doesn't provide options to publish your app as a single file. You'll need to publish manually by following the instructions from the CLI tab. For more information, see [Publish .NET apps with .NET CLI](../deploy-with-cli.md).
114-
115111
---
116112

117113
## Exclude files from being embedded

docs/core/deploying/trimming/trim-self-contained.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -79,10 +79,6 @@ For more information, see [Publish .NET apps with .NET CLI](../deploy-with-cli.m
7979

8080
For more information, see [Publish .NET Core apps with Visual Studio](../deploy-with-vs.md).
8181

82-
### Publish with Visual Studio for Mac
83-
84-
Visual Studio for Mac doesn't provide options to publish your app. You'll need to publish manually by following the instructions from the [Publishing with the CLI](#publish-with-the-cli) section. For more information, see [Publish .NET apps with .NET CLI](../deploy-with-cli.md).
85-
8682
## See also
8783

8884
- [.NET Core application deployment](../index.md).

docs/core/install/macos.md

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -192,22 +192,6 @@ The **x64** .NET SDK installs to its own directory, as described in the previous
192192

193193
Environment variables that add .NET to system path, such as the `PATH` variable, might need to be changed if you have both the x64 and Arm64 versions of the .NET 6 SDK installed. Additionally, some tools rely on the `DOTNET_ROOT` environment variable, which would also need to be updated to point to the appropriate .NET 6 SDK installation folder.
194194

195-
## Install with Visual Studio for Mac
196-
197-
Visual Studio for Mac installs the .NET SDK when the **.NET** workload is selected. To get started with .NET development on macOS, see [Install Visual Studio 2022 for Mac](/visualstudio/mac/installation).
198-
199-
> [!IMPORTANT]
200-
> Visual Studio for Mac is being retired. For more information, see [What's happening to Visual Studio for Mac?](/visualstudio/mac/what-happened-to-vs-for-mac?view=vsmac-2022&preserve-view=true).
201-
202-
| .NET SDK version | Visual Studio version |
203-
| --------------------- | ----------------------------------------------------------------------------------- |
204-
| 8.0 | Visual Studio 2022 for Mac 17.6.1 or higher. (Available as a preview feature only.) |
205-
| 6.0 | Visual Studio 2022 for Mac 17.0 or higher. |
206-
207-
:::image type="content" source="media/install-sdk/mac-install-selection.png" alt-text="macOS Visual Studio 2022 for Mac with the .NET workload selected." lightbox="media/install-sdk/mac-install-selection.png":::
208-
209-
[!INCLUDE [](~/includes/vs-mac-eol.md)]
210-
211195
## Install alongside Visual Studio Code
212196

213197
Visual Studio Code is a powerful and lightweight source code editor that runs on your desktop. Visual Studio Code is available for Windows, macOS, and Linux.
@@ -246,6 +230,5 @@ For more information about using .NET in a Docker container, see [Introduction t
246230

247231
- [How to check if .NET is already installed](how-to-detect-installed-versions.md?pivots=os-macos).
248232
- [Working with macOS Catalina notarization](macos-notarization-issues.md).
249-
- [Tutorial: Get started on macOS](../tutorials/with-visual-studio-mac.md).
250233
- [Tutorial: Create a new app with Visual Studio Code](../tutorials/with-visual-studio-code.md).
251234
- [Tutorial: Containerize a .NET app](../docker/build-container.md).

docs/core/tools/sdk-errors/netsdk1045.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -48,14 +48,6 @@ If you have a preview installed of the requested .NET SDK version, you also need
4848

4949
For example, .NET Core 3.0 and later require Visual Studio 2019. Upgrade to [Visual Studio 2019 version 16.3](https://visualstudio.microsoft.com/downloads) or later to build your project.
5050

51-
## Visual Studio for Mac
52-
53-
VS for Mac supports both `dotnet msbuild` and MSBuild on Mono. But the .NET SDK version is downgraded when MSBuild on Mono is used, and this can result in the NETSDK1045 error.
54-
55-
Open the **Solution Properties** window (ctrl-click the solution in the **Solution** window and select **Properties**), select **Build - General**, and uncheck **Build with MSBuild on Mono**. This **Build with MSBuild on Mono** option will be checked if there are any classic projects in the solution, and this can cause problems since Mono does not support the later .NET SDKs.
56-
57-
For more information about which Visual Studio for Mac 2022 versions support which .NET versions, see [Supported versions of .NET](/visualstudio/mac/supported-versions-net).
58-
5951
## PATH environment variable
6052

6153
The build tools use the PATH environment variable to find the right version of the .NET build tools. If the PATH environment variable contains direct paths to older build tools, this error message could appear. Make sure the only path to the .NET tools in the PATH environment variable is to the top-level *dotnet* folder, for example, *C:\Program Files\dotnet*. An example of an incorrect PATH would be something like *C:\Program Files\dotnet\2.1.0\sdks*.

0 commit comments

Comments
 (0)