Considerations for Deleting Applications from Application Diagrams
In Application Designer, you can delete application definitions from the application diagram. However, deleting application definitions can affect solution items and other distributed system diagrams that reference those applications as well as the application diagram. The following sections contain more information about deleting application definitions and how to resolve conditions that might arise.
Deleting Application Definitions
Restoring Deleted Applications
Deleting Application Definitions
Deleting an application definition has the following effects:
Deletes an unimplemented application completely from the solution.
Deletes an implemented application from the diagram but only removes the associated project from the solution without deleting it.
Note
When you delete an implemented ASP.NET application, then add one with the same name and location the deleted one, and attempt to implement it, you are prompted to create the associated project in a different location, open the existing project and add it back to the solution, or overwrite the existing project. To avoid this prompt, rename the application prior to implementation. For more information, see Considerations for Implementing Applications.
Deletes all connections to the application definition on the application diagram. However, endpoints on connected definitions remain on the application diagram.
Prevents validation of any system diagrams containing a reference to or use of that application definition. The use of that definition remains a member of any systems that reference it and displays squiggly lines to indicate that the underlying definition is missing from the application diagram. For more information, see Troubleshooting System Diagrams.
Prevents validation of any deployment diagrams on which the use of that definition remains bound to a logical server. For more information, see Troubleshooting Deployment Diagrams.
Restoring Deleted Applications
You can resolve conditions that occur from deleting an application definition from the application diagram as follows:
To restore a deleted application definition to the application diagram, you can take the following actions:
Add an application definition of the same type with the same name as the deleted one to the application diagram. For more information, see How to: Define Applications on Application Diagrams and Troubleshooting Application Diagrams.
Note
When you implement an ASP.NET application definition with the same name and location as one that was previously implemented and deleted, you are prompted to choose another location for the project, open the existing project and add it back to the solution, or overwrite the existing project.
For implemented application definitions, add the project back to the solution. For more information, see How to: Reverse-Engineer Projects in Existing Solutions.
To resolve validation errors on system and deployment diagrams, restore the deleted application definition to the application diagram or delete its uses from system diagrams that reference it. For more information, see How to: Delete Members from Application Systems.
Tip
If a bound reference to a deleted application exists on a deployment diagram, and the deployment diagram is open, deleting uses of that application definition from the appropriate system diagram automatically unbinds that reference from the deployment diagram. However, to remove bound references to deleted applications from closed deployment diagrams, open those diagrams and unbind the applications manually. For more information, see How to: Unbind Applications from Logical Servers.
See Also
Tasks
How to: Delete Applications from Application Diagrams
Reference
Considerations for Deleting Endpoints from Applications