Skip to content

Commit 1d12aec

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)
2 parents 0f3b445 + 6a19c5e commit 1d12aec

25 files changed

+206
-462
lines changed

.openpublishing.redirection.json

Lines changed: 36 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1890,6 +1890,11 @@
18901890
"redirect_url": "/visualstudio/install/create-an-offline-installation-of-visual-studio",
18911891
"redirect_document_id": false
18921892
},
1893+
{
1894+
"source_path": "docs/modeling/customizing-presentation-on-the-diagram.md",
1895+
"redirect_url": "/visualstudio/modeling/defining-shapes-and-connectors",
1896+
"redirect_document_id": false
1897+
},
18931898
{
18941899
"source_path": "docs/modeling/deploy-a-layer-model-extension.md",
18951900
"redirect_url": "/visualstudio/modeling/deploy-a-layer-model-extension?view=vs-2015",
@@ -2075,14 +2080,34 @@
20752080
"redirect_url": "/visualstudio/modeling/create-uml-modeling-projects-and-diagrams",
20762081
"redirect_document_id": false
20772082
},
2083+
{
2084+
"source_path": "docs/modeling/working-with-domain-specific-language-solutions.md",
2085+
"redirect_url": "/visualstudio/modeling/about-domain-specific-languages",
2086+
"redirect_document_id": false
2087+
},
2088+
{
2089+
"source_path": "docs/modeling/deploying-domain-specific-language-solutions.md",
2090+
"redirect_url": "/visualstudio/modeling/msi-and-vsix-deployment-of-a-dsl",
2091+
"redirect_document_id": false
2092+
},
20782093
{
20792094
"source_path": "docs/modeling/navigate-the-uml-model.md",
20802095
"redirect_url": "/visualstudio/modeling/create-uml-modeling-projects-and-diagrams",
20812096
"redirect_document_id": false
20822097
},
2098+
{
2099+
"source_path": "docs/modeling/writing-user-commands-and-actions.md",
2100+
"redirect_url": "/visualstudio/modeling/how-to-modify-a-standard-menu-command-in-a-domain-specific-language",
2101+
"redirect_document_id": false
2102+
},
20832103
{
20842104
"source_path": "docs/modeling/nesting-shapes.md",
2085-
"redirect_url": "/visualstudio/modeling/customizing-presentation-on-the-diagram",
2105+
"redirect_url": "/visualstudio/modeling/defining-shapes-and-connectors",
2106+
"redirect_document_id": false
2107+
},
2108+
{
2109+
"source_path": "docs/modeling/properties-of-model-elements.md",
2110+
"redirect_url": "/visualstudio/modeling/properties-of-a-dsl-definition",
20862111
"redirect_document_id": false
20872112
},
20882113
{
@@ -3325,6 +3350,16 @@
33253350
"redirect_url": "/visualstudio/ide/whats-new-visual-studio-2019",
33263351
"redirect_document_id": false
33273352
},
3353+
{
3354+
"source_path": "docs/workflow-designer/workflow-designer-ui-help.md",
3355+
"redirect_url": "/visualstudio/workflow-designer/browse-and-select-a-dotnet-type-dialog-box",
3356+
"redirect_document_id": false
3357+
},
3358+
{
3359+
"source_path": "docs/workflow-designer/using-the-activity-designers.md",
3360+
"redirect_url": "/visualstudio/workflow-designer/control-flow-activity-designers",
3361+
"redirect_document_id": false
3362+
},
33283363
{
33293364
"source_path": "docs/workflow-designer/activity-views-legacy.md",
33303365
"redirect_url": "/visualstudio/workflow-designer/developing-applications-with-the-workflow-designer",

docs/modeling/add-commands-and-gestures-to-layer-diagrams.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ You can define several command and gesture handlers in the same Visual Studio pr
2222
2323
## Requirements
2424

25-
See [Requirements](../modeling/extend-layer-diagrams.md#prereqs).
25+
See [Requirements](../modeling/extend-layer-diagrams.md#requirements).
2626

2727
## Define a Command or Gesture in a New VSIX
2828

docs/modeling/add-custom-architecture-validation-to-layer-diagrams.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can package your layer validation extension into a Visual Studio Integration
2626
2727
## Requirements
2828

29-
See [Requirements](../modeling/extend-layer-diagrams.md#prereqs).
29+
See [Requirements](../modeling/extend-layer-diagrams.md#requirements).
3030

3131
## Defining a Layer Validator in a New VSIX
3232

docs/modeling/analyze-and-model-your-architecture.md

Lines changed: 13 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -3,28 +3,15 @@ title: Analyze and model your architecture
33
ms.date: 11/04/2016
44
ms.topic: conceptual
55
helpviewer_keywords:
6-
- "Visual Studio Ultimate, exploring code"
7-
- "Visual Studio Ultimate, visualizing code"
86
- "diagrams - modeling"
9-
- "Visual Studio ALM, modeling"
10-
- "application, design"
117
- "architecture"
128
- "code visualization"
139
- "application design"
14-
- "applications, architecture"
1510
- "code exploration"
16-
- "Visual Studio ALM, exploring code"
1711
- "modeling"
1812
- "application architecture"
19-
- "application, modeling"
20-
- "applications, modeling"
2113
- "architecture [Visual Studio ALM], modeling"
2214
- "application modeling"
23-
- "Visual Studio Ultimate, modeling"
24-
- "architecture [Visual Studio Ultimate], modeling"
25-
- "application, architecture"
26-
- "Visual Studio ALM, visualizing code"
27-
- "applications, designing"
2815
author: gewarren
2916
ms.author: gewarren
3017
manager: jillfra
@@ -43,22 +30,23 @@ Make sure your app meets architectural requirements by using Visual Studio archi
4330

4431
See [Scenario: Change your design using visualization and modeling](../modeling/scenario-change-your-design-using-visualization-and-modeling.md).
4532

46-
## To
33+
## Article reference
4734

4835
|||
4936
|-|-|
50-
|**Visualize code**:<br /><br /> - See the code's organization and relationships by creating code maps. Visualize dependencies between assemblies, namespaces, classes, methods, and so on.<br />- See the class structure and members for a specific project by creating class diagrams from code.<br />- Find conflicts between your code and its design by creating dependency diagrams to validate code.|- [Visualize code](../modeling/visualize-code.md)<br />- [Working with Classes and Other Types (Class Designer)](../ide/class-designer/designing-and-viewing-classes-and-types.md)<br />- [Video: Understand design from code with Visual Studio 2015 code maps](https://channel9.msdn.com/Events/Visual-Studio/Connect-event-2015/502)<br />- [Video: Validate your architecture dependencies in real time](https://sec.ch9.ms/sessions/69613110-c334-4f25-bb36-08e5a93456b5/170ValidateArchitectureDependenciesWithVisualStudio.mp4)|
51-
|**Define the architecture**:<br /><br /> - Define and enforce constraints on dependencies between the components of your code by creating dependency diagrams.|- [Video: Validate architecture dependencies with Visual Studio (Channel 9)](https://channel9.msdn.com/Events/Connect/2016/170)|
52-
|**Validate your system with the requirements and intended design:**<br /><br /> - Validate code dependencies with dependency diagrams that describe the intended architecture and prevent changes that might conflict with the design.|- [Video: Validate architecture dependencies with Visual Studio (Channel 9)](https://channel9.msdn.com/Events/Connect/2016/170)|
53-
|**Customize models and diagrams**:<br /><br /> - Create your own domain-specific languages.|- [Modeling SDK for Visual Studio - Domain-Specific Languages](../modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md)|
54-
|**Generate text using T4 templates**:<br /><br /> - Use text blocks and control logic inside templates to generate text-based files.<br /> - T4 template build with MSBuild included in Visual Studio|- [Code Generation and T4 Text Templates](../modeling/code-generation-and-t4-text-templates.md)|
55-
|**Share models, diagrams, and code maps using Team Foundation version control**:<br /><br /> - Put code maps, projects, and dependency diagrams under Team Foundation version control so you can share them.| |
37+
|**Visualize code**:<br /><br />- See the code's organization and relationships by creating code maps. Visualize dependencies between assemblies, namespaces, classes, methods, and so on.<br />- See the class structure and members for a specific project by creating class diagrams from code.<br />- Find conflicts between your code and its design by creating dependency diagrams to validate code.|- [Visualize code](../modeling/visualize-code.md)<br />- [Working with Classes and Other Types (Class Designer)](../ide/class-designer/designing-and-viewing-classes-and-types.md)<br />- [Video: Understand design from code with Visual Studio 2015 code maps](https://channel9.msdn.com/Events/Visual-Studio/Connect-event-2015/502)<br />- [Video: Validate your architecture dependencies in real time](https://sec.ch9.ms/sessions/69613110-c334-4f25-bb36-08e5a93456b5/170ValidateArchitectureDependenciesWithVisualStudio.mp4)|
38+
|**Define the architecture**:<br /><br />- Define and enforce constraints on dependencies between the components of your code by creating dependency diagrams.|- [Video: Validate architecture dependencies with Visual Studio (Channel 9)](https://channel9.msdn.com/Events/Connect/2016/170)|
39+
|**Validate your system with the requirements and intended design:**<br /><br />- Validate code dependencies with dependency diagrams that describe the intended architecture and prevent changes that might conflict with the design.|- [Video: Validate architecture dependencies with Visual Studio (Channel 9)](https://channel9.msdn.com/Events/Connect/2016/170)|
40+
|**Customize models and diagrams**:<br /><br />- Create your own domain-specific languages.|- [Modeling SDK for Visual Studio - Domain-Specific Languages](../modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md)|
41+
|**Generate text using T4 templates**:<br /><br />- Use text blocks and control logic inside templates to generate text-based files.<br /> - T4 template build with MSBuild included in Visual Studio|- [Code Generation and T4 Text Templates](../modeling/code-generation-and-t4-text-templates.md)|
42+
|**Share models, diagrams, and code maps using Team Foundation version control**:<br /><br />- Put code maps, projects, and dependency diagrams under Team Foundation version control so you can share them.| |
5643

5744
To see which editions of Visual Studio support each feature, see [Edition support for architecture and modeling tools](../modeling/what-s-new-for-design-in-visual-studio.md#VersionSupport)
5845

5946
## Types of models and typical uses
6047

6148
### Code maps
49+
6250
Code maps help you see the organization and relationships in your code.
6351

6452
**Typical uses:**
@@ -71,8 +59,9 @@ Code maps help you see the organization and relationships in your code.
7159
- [Use code maps to debug your applications](../modeling/use-code-maps-to-debug-your-applications.md)
7260
- [Find potential problems using code map analyzers](../modeling/find-potential-problems-using-code-map-analyzers.md)
7361

74-
### Dependency diagram
75-
Dependency diagrams let you define the structure of an application as a set of layers or blocks with explicit dependencies. You can run validation to discover conflicts between dependencies in the code and dependencies described on a dependency diagram.
62+
### Dependency diagrams
63+
64+
Dependency diagrams let you define the structure of an application as a set of layers or blocks with explicit dependencies. Live validation shows conflicts between dependencies in the code and dependencies described on a dependency diagram.
7665

7766
**Typical uses:**
7867

@@ -86,7 +75,8 @@ Dependency diagrams let you define the structure of an application as a set of l
8675
- [Validate code with dependency diagrams](../modeling/validate-code-with-layer-diagrams.md)
8776

8877
### Domain-specific language (DSL)
89-
A DSL is a notation that you design for a specific purpose. In Visual Studio, it is usually graphical.
78+
79+
A DSL is a notation that you design for a specific purpose. In Visual Studio, it's usually graphical.
9080

9181
**Typical uses:**
9282

@@ -97,10 +87,6 @@ A DSL is a notation that you design for a specific purpose. In Visual Studio, it
9787

9888
- [Modeling SDK for Visual Studio - Domain-Specific Languages](../modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md)
9989

100-
## Where can I get more information?
101-
102-
[Visual Studio Visualization & Modeling Tools Forum](http://go.microsoft.com/fwlink/?LinkId=184720)
103-
10490
## See also
10591

10692
- [What's new for modeling in Visual Studio 2017](../modeling/what-s-new-for-design-in-visual-studio.md)

docs/modeling/creating-custom-t4-text-template-directive-processors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ manager: jillfra
1010
ms.workload:
1111
- "multiple"
1212
---
13-
# Creating Custom T4 Text Template Directive Processors
13+
# Create Custom T4 Text Template Directive Processors
1414

1515
The *text template transformation process* takes a *text template* file as the input and produces a text file as the output. The *text template transformation engine* controls the process, and the engine interacts with a text template transformation host and one or more text template *directive processors* to complete the process. For more information, see [The Text Template Transformation Process](../modeling/the-text-template-transformation-process.md).
1616

docs/modeling/customizing-and-extending-a-domain-specific-language.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,31 +10,30 @@ manager: jillfra
1010
ms.workload:
1111
- "multiple"
1212
---
13-
# Customizing and Extending a Domain-Specific Language
14-
Visual Studio Modeling and Visualization SDK (VMSDK) provides several levels at which you can define modeling tools:
13+
# Customize and extend a domain-specific language
1514

16-
1. Define a domain-specific language (DSL) using the DSL Definition diagram. You can quickly create a DSL with a diagrammatic notation, a readable XML form, and the basic tools that are required to generate code and other artifacts.
15+
Visual Studio Modeling and Visualization SDK (VMSDK) provides several levels at which you can define modeling tools:
1716

18-
For more information, see [How to Define a Domain-Specific Language](../modeling/how-to-define-a-domain-specific-language.md).
17+
1. Define a domain-specific language (DSL) using the DSL Definition diagram. You can quickly create a DSL with a diagrammatic notation, a readable XML form, and the basic tools that are required to generate code and other artifacts. For more information, see [How to Define a Domain-Specific Language](../modeling/how-to-define-a-domain-specific-language.md).
1918

2019
2. Fine-tune the DSL by using more advanced features of the DSL Definition. For example, you can make additional links appear when the user creates an element. These techniques are mostly achieved in the DSL Definition, and some require a few lines of program code.
2120

22-
3. Extend your modeling tools by using program code. VMSDK is designed specifically to make it easy to integrate your extensions with the code that is generated from the DSL Definition. For more information, see [Writing Code to Customize a Domain-Specific Language](../modeling/writing-code-to-customise-a-domain-specific-language.md).
21+
3. Extend your modeling tools by using program code. VMSDK is designed specifically to make it easy to integrate your extensions with the code that is generated from the DSL Definition. For more information, see [Writing Code to Customize a Domain-Specific Language](../modeling/writing-code-to-customise-a-domain-specific-language.md).
2322

2423
> [!NOTE]
25-
> When you have updated the DSL Definitions file, do not forget to click **Transform All Templates** in the toolbar of Solution Explorer before rebuilding your solution.
24+
> When you have updated the DSL Definitions file, don't forget to click **Transform All Templates** in the toolbar of **Solution Explorer** before rebuilding your solution.
2625
27-
## <a name="customShapes"></a> In this Section
26+
## Article reference
2827

2928
|To achieve this effect|Refer to this topic|
3029
|-|-|
31-
|Allow the user to set the color and style properties of a shape.|Right-click the shape or connector class, point to **Add Exposed**, and click an item.<br /><br /> See [Customizing Presentation on the Diagram](../modeling/customizing-presentation-on-the-diagram.md).|
30+
|Allow the user to set the color and style properties of a shape.|Right-click the shape or connector class, point to **Add Exposed**, and click an item.|
3231
|Different classes of model element look similar on the diagram, sharing properties such as initial height and width, color, tooltips.|Use inheritance between shapes or connector classes. Mappings between derived shapes and derived domain classes inherit the mapping details of the parents.<br /><br /> Or, map different domain classes to the same shape class.|
3332
|A class of model element is displayed by different shapes contexts.|Map more than one shape class to the same domain class. When you build the solution, follow the error report and provide the requested code to decide what shape to use.|
3433
|Shape color or other features such as font indicate current state.|See [Updating Shapes and Connectors to Reflect the Model](../modeling/updating-shapes-and-connectors-to-reflect-the-model.md).<br /><br /> Create a rule that updates the exposed properties. See [Rules Propagate Changes Within the Model](../modeling/rules-propagate-changes-within-the-model.md).<br /><br /> Or, use OnAssociatedPropertyChanged() to update non-exposed features such as link arrows or font.|
3534
|Icon on shape changes to indicate state.|Set the visibility of the decorator mapping in the DSL Details window. Locate several image decorators on the same position. See [Updating Shapes and Connectors to Reflect the Model](../modeling/updating-shapes-and-connectors-to-reflect-the-model.md).<br /><br /> Or, override `ImageField.GetDisplayImage()`. See example in <xref:Microsoft.VisualStudio.Modeling.Diagrams.ImageField>.|
36-
|Set a background image on any shape|Override InitializeInstanceResources() to add an anchored ImageField. See [Customizing Presentation on the Diagram](../modeling/customizing-presentation-on-the-diagram.md).|
37-
|Nest shapes to any depth|Set up a recursive embedding tree. Define BoundsRules to contain the shapes. See [Customizing Presentation on the Diagram](../modeling/customizing-presentation-on-the-diagram.md).|
35+
|Set a background image on any shape|Override InitializeInstanceResources() to add an anchored ImageField.|
36+
|Nest shapes to any depth|Set up a recursive embedding tree. Define BoundsRules to contain the shapes.|
3837
|Attach connectors at fixed points on an element's boundary.|Define embedded terminal elements, represented by small ports on the diagram. Use BoundsRules to fix the ports in place. See the Circuit Diagram sample at [Visualization and Modeling SDK](http://go.microsoft.com/fwlink/?LinkID=186128).|
3938
|Text field displays a value derived from other values.|Map the text decorator to a Calculated or Custom Storage domain property. For more information, see [Calculated and Custom Storage Properties](../modeling/calculated-and-custom-storage-properties.md).|
4039
|Propagate changes between model elements, or between shapes|See [Validation in a Domain-Specific Language](../modeling/validation-in-a-domain-specific-language.md).|

docs/modeling/customizing-presentation-on-the-diagram.md

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

docs/modeling/deploying-domain-specific-language-solutions.md

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

0 commit comments

Comments
 (0)