Skip to content

Commit 7cf77e1

Browse files
Merge pull request #14025 from MicrosoftDocs/main
Merged by Learn.Build PR Management system
2 parents e829bff + db67fe4 commit 7cf77e1

17 files changed

+67
-203
lines changed

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1640,6 +1640,21 @@
16401640
"redirect_url": "/previous-versions/visualstudio/visual-studio-2017/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework",
16411641
"redirect_document_id": false
16421642
},
1643+
{
1644+
"source_path": "docs/ide/reference/property-pages-javascript-esproj.md",
1645+
"redirect_url": "/visualstudio/javascript/property-pages-javascript-esproj",
1646+
"redirect_document_id": false
1647+
},
1648+
{
1649+
"source_path": "docs/ide/reference/debug-page-project-designer.md",
1650+
"redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/debug-page-project-designer",
1651+
"redirect_document_id": false
1652+
},
1653+
{
1654+
"source_path": "docs/ide/reference/code-snippet-picker.md",
1655+
"redirect_url": "/visualstudio/ide/code-snippets",
1656+
"redirect_document_id": false
1657+
},
16431658
{
16441659
"source_path": "docs/ide/reference/signing-page-project-designer.md",
16451660
"redirect_url": "/visualstudio/ide/how-to-sign-application-and-deployment-manifests",
Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,35 @@
11
---
2-
title: Database projects & DAC projects (.NET Framework)
3-
description: Explore database projects and data-tier applications (DACs) to create new databases and new DACs, and update existing databases and DACs.
4-
ms.date: 11/01/2023
5-
ms.topic: conceptual
2+
title: Database Projects & DAC Projects (.NET Framework)
3+
description: Explore database projects and data-tier applications (DACs), create databases and DACs, and update existing databases and DACs.
4+
ms.date: 06/24/2025
5+
ms.topic: concept-article
66
helpviewer_keywords:
77
- databases, managing change
88
author: ghogen
99
ms.author: ghogen
1010
manager: mijacobs
1111
ms.subservice: data-tools
12+
#customer intent: As a developer, I want to explore database projects and data-tier applications (DACs) in Visual Studio, so I can create and updated databases and DACs.
1213
---
1314

1415
# Database projects and data-tier applications (.NET Framework)
1516

1617
[!INCLUDE [Data access tech note](./includes/data-technology-note.md)]
1718

18-
You can use database projects to create new databases, new data-tier applications (DACs), and to update existing databases and data-tier applications. Both database projects and DAC projects enable you to apply version control and project management techniques to your database development efforts in much the same way that you apply those techniques to managed or native code. You can help your development team manage changes to databases and database servers by creating a DAC project, database project, or a server project and putting it under version control. Members of your team can then check out files to make, build, and test changes in an isolated development environment, or sandbox, before sharing them with the team. To help ensure code quality, your team can finish and test all changes for a particular release of the database in a staging environment before you deploy the changes into production.
19+
You can use database projects to create new databases and new data-tier applications (DACs) and update existing databases and DACs. Both database projects and DAC projects enable you to apply version control and project management techniques to your database development efforts in much the same way you apply those techniques to managed or native code. You can help your development team manage changes to databases and database servers by creating a DAC project, database project, or a server project and putting it under version control. Members of your team can then check out files to make, build, and test changes in an isolated development environment, or sandbox, before sharing them with the team. To help ensure code quality, your team can finish and test all changes for a particular release of the database in a staging environment before you deploy the changes into production.
1920

20-
For a list of the database features that are supported by data-tier applications, see [DAC support for SQL Server objects](/sql/relational-databases/data-tier-applications/dac-support-for-sql-server-objects-and-versions). If you use features in your database that are not supported by data-tier applications, you should instead use a database project to manage changes to your database.
21+
To review the list of the supported database features for data-tier applications, see [DAC support for SQL Server objects](/sql/relational-databases/data-tier-applications/dac-support-for-sql-server-objects-and-versions). If you use unsupported features in your database, you should instead use a database project to manage changes to your database.
2122

2223
## Common high-level tasks
2324

24-
| High-Level Task | Supporting Content |
25-
| - | - |
26-
| **Start development of a data-tier application:** The concept of a data-tier application (DAC) was introduced with SQL Server 2008. A DAC contains the definition for a SQL Server database and the supporting instance objects that are used by a client-server or 3-tier application. A DAC includes database objects, such as tables and views, together with instance entities such as logins. You can use Visual Studio to create a DAC project, build a DAC package file, and send the DAC package file to a database administrator for deployment onto an instance of the SQL Server Database Engine. | - [Data-tier applications](/sql/relational-databases/data-tier-applications/data-tier-applications)<br />- [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) |
27-
| **Performing iterative database development:** Developers can check out parts of the project and update them in an isolated development environment. By using this type of environment, you can test your changes without affecting other members of the team. After the changes are complete, you check the files back into version control, where other team members can obtain your changes and build and deploy them to a test server. | - [Project-oriented offline database development (SQL Server Data Tools)](/sql/ssdt/project-oriented-offline-database-development)<br />- [Transact-SQL debugger (SQL Server Management Studio)](/sql/ssms/scripting/transact-sql-debugger) |
28-
| **Prototyping, verifying test results, and modifying database scripts and objects:** You can use the Transact-SQL editor to perform any one of these common tasks. | - [Query and text editors (SQL Server Management Studio)](/sql/ssms/scripting/query-and-text-editors-sql-server-management-studio) |
25+
The following table describes the common high-level tasks you can accomplish for your database projects and data-tier applications in Visual Studio:
26+
27+
| High-level task | Description | Supporting content |
28+
|-----------------|-------------|--------------------|
29+
| **Start development of a data-tier application** | The concept of a data-tier application (DAC) was introduced with SQL Server 2008. A DAC contains the definition for a SQL Server database and the supporting instance objects that are used by a client-server or three-tier application. A DAC includes database objects, such as tables and views, together with instance entities like logins. You can use Visual Studio to create a DAC project and build a DAC package file. Then you can send the DAC package file to a database administrator for deployment onto an instance of the SQL Server Database Engine. | - [Data-tier applications](/sql/relational-databases/data-tier-applications/data-tier-applications)<br />- [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) |
30+
| **Perform iterative database development** | Developers can check out parts of the project and make updates in an isolated development environment. By using this type of environment, you can test your changes without affecting other members of the team. After the changes are complete, you check the files back into version control, where other team members can obtain your changes and build and deploy them to a test server. | - [Project-oriented offline database development (SQL Server Data Tools)](/sql/ssdt/project-oriented-offline-database-development)<br />- [Transact-SQL debugger (SQL Server Management Studio)](/sql/ssms/scripting/transact-sql-debugger) |
31+
| **Prototype, verify test results, modify database scripts and objects** | You can use the Transact-SQL editor to perform any of these common tasks. | - [Query and text editors (SQL Server Management Studio)](/sql/ssms/scripting/query-and-text-editors-sql-server-management-studio) |
2932

3033
## Related content
3134

32-
- [Visual Studio data tools for .NET](../data-tools/visual-studio-data-tools-for-dotnet.md)
35+
- [Visual Studio data tools for .NET](../data-tools/visual-studio-data-tools-for-dotnet.md)
Lines changed: 21 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,46 @@
11
---
2-
title: Design Windows Forms applications
3-
description: 'Explore Windows Forms Designer in Visual Studio for rapid application development: arrange controls, set margins and padding, adjust layout, size, and display.'
4-
ms.date: 08/09/2019
2+
title: Design Windows Forms Applications
3+
description: Explore Windows Forms Designer in Visual Studio for rapid application development. Arrange controls, set margins and padding, and adjust the layout, size, and display of forms.
4+
ms.date: 06/24/2025
55
ms.topic: overview
66
helpviewer_keywords:
77
- Windows Forms Designer
88
author: ghogen
99
ms.author: ghogen
1010
manager: mijacobs
1111
ms.subservice: ui-designers
12+
#customer intent: As a developer, I want to use Windows Forms Designer in Visual Studio, so I can arrange controls, set margins and padding, and adjust the layout, size, and display of forms.
1213
---
13-
# Windows Forms Designer overview
14+
# What is Windows Forms Designer?
1415

15-
Windows Forms Designer in Visual Studio provides a rapid development solution for creating Windows Forms-based applications. Windows Forms Designer lets you easily add controls to a form, arrange them, and write code for their events. For more information about Windows Forms, see [Windows Forms overview](/dotnet/framework/winforms/windows-forms-overview).
16+
Windows Forms Designer in Visual Studio provides a rapid development solution for creating Windows Forms-based applications. Windows Forms Designer lets you easily add controls to a form, arrange them, and write code for their events. For more information about Windows Forms, see [Windows Forms overview](/dotnet/desktop/winforms/overview/).
1617

17-
## Functionality
18+
## Explore the functionality
1819

19-
Using the designer you can:
20+
Here are some of the tasks you can complete with Windows Forms Designer:
2021

2122
- Add components, data controls, or Windows-based controls to a form.
2223

23-
- Double-click the form in the designer and write code in the `Load` event for that form, or double-click a control on the form and write code for the control's default event.
24+
- Double-click the form in the designer and write code in the `Load` event for that form. Double-click a control on the form and write code for the control's default event.
2425

25-
- Edit a control's Text property by selecting the control and typing a name.
26+
- Edit a control's **Text** property by selecting the control and entering a name.
2627

27-
- Adjust the placement of the selected control by moving it with the mouse or the arrow keys. Similarly, adjust the placement more precisely using the Ctrl and arrow keys. Finally, adjust the size of the control by using the Shift and arrow keys.
28+
- Adjust the placement of the selected control by moving it with the mouse or the arrow keys (**Up**, **Down**, **Left**, **Right**). Adjust the placement more precisely by selecting **Ctrl** + the arrow keys. Adjust the size of the control by selecting **Shift** + the arrow keys.
2829

29-
- Select multiple controls by selecting either **Shift** or **Ctrl** while you click. When using **Shift**+click, the first control selected is the dominant control when aligning or manipulating size. When using **Ctrl**+click, the last control selected is dominant, so the dominant control changes with every new control added. Alternatively, you can select multiple controls by dragging a selection rectangle around the controls that you want to select.
30+
- Access multiple form controls simultaneously with **Shift** or **Ctrl** followed by the control shortcut. When you select **Shift** + \<Control shortcut>, the first control you select is the dominant control as you align windows and adjust the size. When you select **Ctrl** + \<Control shortcut>, the last control you select is dominant. This approach allows the dominant control to change to the new control each time you add a control. Another approach is to select multiple controls by dragging a selection rectangle around the controls that you want to select.
3031

31-
> [!NOTE]
32-
> Use Windows Forms Designer, and not the Resource Editor, to make changes to a form's resource (*.resx*) file. If you edit a form-based .resx file, you'll see a warning that changes you make in the Resource Editor may be lost. This is because the Windows Forms Designer generates the .resx file.
32+
## Review caution scenarios
3333

34-
> [!CAUTION]
35-
> Windows Forms Designer executes application code when displaying controls or forms on the design surface. Only open projects from [trusted locations](..\ide\reference\trust-settings.md).
34+
When you work with Windows Forms Designer in Visual Studio, exercise caution in the following scenarios:
3635

37-
> [!CAUTION]
38-
> Resources in `.resx` files may be serialized using `BinaryFormatter`, which is [not secure](/dotnet/standard/serialization/binaryformatter-security-guide). Only use Windows Forms Designer to work with forms and controls that you trust.
36+
- Windows Forms Designer executes application code when displaying controls or forms on the design surface. To ensure executed application code is safe for your system, open projects only from [files and folders configured with trust settings](..\ide\reference\trust-settings.md).
3937

40-
## See also
38+
- Changes to the resource (*.resx*) file for a form should be made with Windows Forms Designer only and not the Resource Editor. If you edit a form-based *.resx* file, changes made outside the designer can be lost.
39+
40+
- Resources in a _.resx_ file can be serialized by using the [BinaryFormatter](/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter) type. However, this type presents deserialization risks. The type is [insecure and not trustworthy](/dotnet/standard/serialization/binaryformatter-security-guide). Use Windows Forms Designer to work only with forms and controls that you trust.
41+
42+
## Related content
4143

4244
- [Windows Forms overview](/dotnet/framework/winforms/windows-forms-overview)
4345
- [Windows Forms controls](/dotnet/framework/winforms/controls/)
44-
- [User input in Windows Forms](/dotnet/framework/winforms/user-input-in-windows-forms)
45-
- [Data binding in Windows Forms](/dotnet/framework/winforms/windows-forms-data-binding)
46-
- [Enhance Windows Forms apps](/dotnet/framework/winforms/advanced/)
47-
- [System.Windows.Forms API reference](/dotnet/api/system.windows.forms)
46+
- [User input in Windows Forms](/dotnet/framework/winforms/user-input-in-windows-forms)

docs/ide/code-snippets.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.topic: conceptual
66
f1_keywords:
77
- vs.ExpansionManagerImport
88
- vs.codesnippetmanager
9+
- vs.expansionpicker
910
helpviewer_keywords:
1011
- surround with
1112
- code snippets

docs/ide/fsharp-visual-studio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ The following table summarizes features in project properties for F#:
5858
|Application|[Application Page, Project Designer](reference/application-page-project-designer-csharp.md)|Enables you to specify application-level settings and properties, such as whether you are creating a library or an executable file, what version of .NET the application targets, and information about where the resource files that the application uses are stored.|
5959
|Build|[Build Page, Project Designer](reference/build-page-project-designer-csharp.md)|Enables you to control how the code is compiled.|
6060
|Build Events|[Build Events Page, Project Designer](reference/build-events-page-project-designer-csharp.md)|Enables you to specify commands to run before or after a compilation.|
61-
|Debug|[Debug Page, Project Designer](reference/debug-page-project-designer.md)|Enables you to control how the application runs during debugging. This includes what commands to use and what your application's starting directory is, and any special debugging modes you want to enable, such as native code and SQL.|
61+
|Debug|[Debug Page, Project Designer](/previous-versions/visualstudio/visual-studio-2017/ide/reference/debug-page-project-designer)|Enables you to control how the application runs during debugging. This includes what commands to use and what your application's starting directory is, and any special debugging modes you want to enable, such as native code and SQL.|
6262
|Package (.NET SDK only)|N/A|Enables you to define NuGet Package metadata when publishing as a NuGet package.|
6363
|Reference Paths|[Manage references in a project](managing-references-in-a-project.md)|Enables you to specify where to search for assemblies that the code depends on.|
6464
|Resources (.NET SDK only)|N/A|Enables you to generate and manage a default resources file.|

docs/ide/reference/code-snippet-picker.md

Lines changed: 0 additions & 57 deletions
This file was deleted.

0 commit comments

Comments
 (0)