Implementing Applications on Application Diagrams
In Application Designer, you can implement applications at any time to generate a skeleton implementation, which includes the appropriate projects for those applications. These projects can include code or class files, configuration files, and any other resources needed to continue defining applications in code.
In This Section
Describes considerations to make before implementing applications. |
|
Describes how to change the names of projects generated for applications. |
|
Describes how to choose the Web site type (file system-based or HTTP-based) for ASP.NET applications. |
|
Assigning Project Templates to Applications on Application Diagrams |
Contains topics about choosing project templates used to generate projects for applications. |
Describes how to generate a skeleton implementation to continue defining applications in code. |
Related Sections
Introduces Distributed System Designers, common tasks performed across designers, accessibility information, and walkthroughs. |
|
Introduces Application Designer, which you can use to design, configure, and connect applications within a solution. |
|
Contains topics about designing applications using Application Designer and the application diagram in your solution. |
|
Contains topics about describing how to configure connections between applications in the development environment. |
|
Describes and helps resolve issues that can affect application diagrams and other items in the solution. |
|
Describes common tasks you can perform across designers in Distributed System Designers. |
|
Provides walkthroughs through core tasks you can perform using Distributed System Designers. |