Considerations for Deleting Endpoints from Applications
In Application Designer, deleting endpoints from application definitions can affect solution items and other distributed system diagrams that reference those endpoints as well as the application diagram.
Deleting Endpoints from Application Definitions
Deleting an application endpoint affects other distributed system diagrams as well as the application diagram in the following ways:
Deletes all connections to that endpoint on the application diagram. However, endpoints connected to that endpoint are not deleted.
Deletes any references and connections to that endpoint on any open system diagrams. Any proxy endpoints and delegations associated with that endpoint are also deleted. If any references to the deleted endpoint exist on closed system diagrams, those references are removed when you open those diagrams. For more information, see Troubleshooting System Diagrams.
Depending on the application and endpoint type, deleting an implemented endpoint also deletes any associated project files or entries in code and configuration files from disk.
The following sections contain more information about deleting implemented Web service endpoints.
Deleting Implemented Web Service Provider Endpoints
If you delete an implemented .NET Web Service provider endpoint from an ASP.NET application, Visual Studio also deletes the associated .asmx file. If you delete an .asmx file from the application's project, Visual Studio also deletes the corresponding .NET Web Service provider endpoint.
Note
Deleting a .NET Web Service provider endpoint or its .asmx file does not remove the associated Web service class file, any class or class diagram files for user-defined types referenced by operations or parameters defined by the endpoint, or any associated Web references in consumer application projects.
Deleting Implemented Web Service Consumer Endpoints
When you delete implemented Web service consumer endpoints, be aware of the following considerations:
When an implemented Web service consumer endpoint represents an automatically generated Web service client proxy class, deleting such an endpoint from a Web service consumer application deletes the associated Web reference. Similarly, deleting a Web reference that generates a dynamic proxy class deletes the corresponding Web service consumer endpoint.
When an implemented Web service consumer endpoint represents a custom Web service client proxy class, deleting such an endpoint from an ASP.NET, Windows, or Office application removes the associated entry from the configuration file in the application project. It does not delete the associated custom proxy class.
For ASP.NET Web applications, deleting or renaming a custom Web service client proxy class removes the associated Web service consumer endpoint because no proxy class name matches the associated appSettings or applicationSettings entry in the Web.config configuration file.
Tip
Adding back a Web service client proxy class with a matching name or renaming an existing proxy class to match the appSettings or applicationSettings Web.config configuration file entry causes the endpoint to reappear.
For Windows and Office applications, deleting or renaming a custom Web service client proxy class does not remove the corresponding Web service consumer endpoint as long as the associated applicationSettings entry exists in the App.config configuration file and the setting is designated as a WebServiceURL type in the Settings pane under the Windows or Office application project properties.
Deleting an implemented Web service consumer endpoint that represents a Web reference or custom Web service client proxy class defined in a referenced project or assembly deletes the associated entry from the configuration file in the application project. However, the Web reference or custom proxy class remains intact.
For more information, see Considerations for Custom Web Service Client Proxy Classes.
See Also
Tasks
How to: Delete Endpoints from Applications
Reference
Considerations for Deleting Applications from Application Diagrams