Skip to content

Commit e1dec48

Browse files
committed
Merged main into live
2 parents 5c1a417 + cf78ae7 commit e1dec48

File tree

2 files changed

+22
-6
lines changed

2 files changed

+22
-6
lines changed

docs/designers/walkthrough-windows-forms-designer.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Windows Forms Designer tutorial
33
description: 'Use Windows Forms Designer to build applications and arrange controls, set margins and padding, adjust layout, size, and display, and set property values.'
4-
ms.date: 08/27/2024
4+
ms.date: 8/5/2025
55
ms.topic: tutorial
66
helpviewer_keywords:
77
- Windows Forms Designer, get started
@@ -30,6 +30,22 @@ When you're finished, you'll have a custom control that's been assembled by usin
3030
> [!TIP]
3131
> If you're a C++ developer and are looking for a tutorial to help you create a Windows app that includes forms and controls, see [Creating a forms-based MFC application](/cpp/mfc/reference/creating-a-forms-based-mfc-application?view=msvc-170&preserve-view=true). For more generalized info, see [Overview of Windows programming in C++](/cpp/windows/overview-of-windows-programming-in-cpp?view=msvc-170&preserve-view=true).
3232
33+
## Prerequisites
34+
35+
::: moniker range="=vs-2019"
36+
37+
- If you don't have Visual Studio, go to [Visual Studio downloads](https://visualstudio.microsoft.com/vs/) to install it for free.
38+
- The **.NET desktop development** workload. To verify or install this workload in Visual Studio, select **Tools** > **Get Tools and Features**. For more information, see [Change workloads or individual components](../install/modify-visual-studio.md#change-workloads-or-individual-components).
39+
40+
::: moniker-end
41+
42+
::: moniker range=">=vs-2022"
43+
44+
- If you don't have Visual Studio, go to [Visual Studio 2022 downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-create-csharp-winform-app-page-cta) to install it for free.
45+
- The **.NET desktop development** workload. To verify or install this workload in Visual Studio, select **Tools** > **Get Tools and Features**. For more information, see [Change workloads or individual components](../install/modify-visual-studio.md#change-workloads-or-individual-components).
46+
47+
::: moniker-end
48+
3349
## Create the custom control project
3450

3551
The first step is to create the DemoCalculator control project.

docs/msbuild/how-to-use-environment-variables-in-a-build.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'Use Environment Variables in a Build'
33
description: Work with environment variables in MSBuild project files, and use environment variables to set build options without modifying the project file.
4-
ms.date: 08/14/2024
4+
ms.date: 8/5/2025
55
ms.topic: how-to
66
helpviewer_keywords:
77
- environment variables, referencing
@@ -14,11 +14,11 @@ ms.subservice: msbuild
1414
---
1515
# Use environment variables in a build
1616

17-
When you build projects, it is often necessary to set build options using information that is not in the project file or the files that comprise your project. This information is typically stored in environment variables.
17+
When you build projects, it's often necessary to set build options using information that isn't in the project file or the files that comprise your project. This information is typically stored in environment variables.
1818

1919
## Reference environment variables
2020

21-
All environment variables that are valid MSBuild property names are available to the Microsoft Build Engine (MSBuild) project file as properties. Valid property names are described in [MSBuild properties](msbuild-properties.md). For example, environment variables that begin with a number are not available in MSBuild.
21+
All environment variables that are valid MSBuild property names are available to the MSBuild project file as properties. Valid property names are described in [MSBuild properties](msbuild-properties.md). For example, environment variables that begin with a number aren't available in MSBuild.
2222

2323
> [!NOTE]
2424
> If the project file contains an explicit definition of a property that has the same name as an environment variable, the property in the project file overrides the value of the environment variable.
@@ -29,11 +29,11 @@ When you build projects, it is often necessary to set build options using inform
2929

3030
`<FinalOutput>$(BIN_PATH)\MyAssembly.dll</FinalOutput>`
3131

32-
You can use a `Condition` attribute to provide a default value for a property if the environment variable was not set.
32+
You can use a `Condition` attribute to provide a default value for a property if the environment variable wasn't set.
3333

3434
#### To provide a default value for a property
3535

36-
- Use a `Condition` attribute on a property to set the value only if the property has no value. For example, the following code sets the `ToolsPath` property to *c:\tools* only if the `ToolsPath` environment variable is not set:
36+
- Use a `Condition` attribute on a property to set the value only if the property has no value. For example, the following code sets the `ToolsPath` property to *c:\tools* only if the `ToolsPath` environment variable isn't set:
3737

3838
`<ToolsPath Condition="'$(TOOLSPATH)' == ''">c:\tools</ToolsPath>`
3939

0 commit comments

Comments
 (0)