Skip to content

Repo sync for protected CLA branch #7044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 13, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions docs/ide/how-to-change-the-build-output-directory.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: 'How to: Change the build output directory'
description: Learn how you can specify the location of output generated by your project on a per-configuration basis (for debug, release, or both).
ms.custom: SEO-VS-2020
ms.date: 05/15/2019
ms.date: 09/10/2021
ms.technology: vs-ide-compile
ms.topic: how-to
helpviewer_keywords:
Expand Down Expand Up @@ -38,10 +38,16 @@ You can specify the location of output generated by your project on a per-config

Type in the path to generate output to (absolute or relative to the root project directory), or choose **Browse** to browse to that folder instead.

::: moniker range="<=vs-2019"
![Output path property for a Visual Studio C# project](media/output-path.png)

::: moniker-end
::: moniker range=">=vs-2022"
![Output path property for a Visual Studio C# project](media/vs-2022/output-path.png)
::: moniker-end

> [!NOTE]
> Some projects will by default include framework and runtime in the build path. To change this, right-click the project node in **Solution Explorer**, select **Edit Project File**, and add the following:

> ```xml
> <PropertyGroup>
> <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
Expand All @@ -52,7 +58,12 @@ You can specify the location of output generated by your project on a per-config
> [!TIP]
> If the output is not being generated to the location that you specified, make sure you're building the corresponding configuration (for example, **Debug** or **Release**) by selecting it on the menu bar of Visual Studio.
>
> ::: moniker range="<=vs-2019"
> ![Build configuration picker in Visual Studio 2019](media/build-configuration-chooser.png)
> ::: moniker-end
> ::: moniker range=">=vs-2022"
> ![Build configuration picker in Visual Studio 2019](media/vs-2022/build-configuration-chooser.png)
> ::: moniker-end

## See also

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/ide/media/vs-2022/output-path.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
74 changes: 73 additions & 1 deletion gamedev/unity/change-log-visual-studio-tools-for-unity.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: "Change Log (Visual Studio Tools for Unity, Windows) | Microsoft Docs"
description: View the change log for Visual Studio Tools for Unity, Windows. See changes from version 1.0.0.0 through 4.7.0.0 and beyond.
ms.custom: ""
ms.date: "6/2/2021"
ms.date: "9/7/2021"
ms.technology: vs-unity-tools
ms.prod: visual-studio-dev16
ms.topic: "conceptual"
Expand All @@ -17,6 +17,78 @@ ms.workload:

Visual Studio Tools for Unity change log.

## 4.11.4.0
Released September 14, 2021

### New Features

- **Integration:**

- Automatically disable asset-indexing for large Unity projects.

### Bug fixes

- **Integration:**

- Fixed supported expression detection with [`UNT0024`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0024.md) diagnostic.

## 4.11.3.0
Released August 10, 2021

### Bug fixes

- **Integration:**

- Reduced memory consumption when processing assets.

- Optimized allocations with [`USP0008`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/USP0008.md), [`USP0009`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/USP0009.md), [`USP0010`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/USP0010.md) and [`USP0011`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/USP0011.md) suppressors.

- Optimized symbol usage with [`UNT0002`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0002.md), [`UNT0003`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0003.md), [`UNT0012`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0012.md), [`UNT0014`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0014.md) diagnostics.

## 4.11.2.0
Released July 13, 2021

### Bug fixes

- **Integration:**

- Improved light-build time, by only running suppressors able to handle CS compiler warnings. All other analyzers will run through solution analysis.

## 4.11.1.0
Released June 15, 2021

### Bug fixes

- **Integration:**

- Reduced memory consumption when parsing yaml assets.

## 4.11.0.0
Released May 25, 2021

### New Features

- **Integration:**

- Added [`UNT0025`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0025.md) diagnostic. Prefer Input.GetKey overloads with KeyCode argument.

- Added more invalid usages (static and readonly fields) to [`UNT0013`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0013.md) diagnostic.

### Bug fixes

- **Integration:**

- Fixed issues with explicit method implementations and [`UNT0006`](https://github.com/microsoft/Microsoft.Unity.Analyzers/blob/main/doc/UNT0006.md) diagnostic.

## 4.10.3.0
Released June 8, 2021

### Bug fixes

- **Integration:**

- [Backported] Reduced memory consumption when parsing yaml assets.

## 4.10.2.0
Released May 25, 2021

Expand Down