How to: Rename Endpoints on Applications
In Application Designer, you can rename endpoints on applications, depending on the endpoint type. For more information, see Overview of Endpoints on Applications.
When renaming an endpoint, be aware of the following considerations:
Endpoint names on an application must be unique. Endpoint names must not conflict with resource names or, if within a system, the names of system members.
Characters that are incompatible with the System Definition Model (SDM) are omitted from names. If the resulting name conflicts with another name or a reserved SDM name, an ordinal is appended to the name or incremented if one already exists. For more information about SDM, see Overview of the System Definition Model (SDM).
You can rename endpoints as needed prior to implementation. However, once an endpoint is implemented, renaming the endpoint affects associated project files in different ways depending on the endpoint.
Be aware of the following considerations when renaming Web service provider endpoints:
The name of a Web service provider endpoint is based on the WSDL service name by default. For example, the first time a Web service endpoint is reverse-engineered, the name of the endpoint is based on the WSDL service name.
Renaming the endpoint renames the Web service class name if it is the same as the endpoint name.
Note
Renaming the Web service class name renames the Web service class file name and the WSDL service name if they are the same as the Web service class name. Renaming the WSDL service name renames the .asmx file name and the WSDL binding name if they are the same as the WSDL service name.
Therefore, if you change the endpoint name, it is possible for this change to propagate from the endpoint name to the class name, from the class name to the WSDL service name, from the WSDL service name to the .asmx file name, and then the WSDL binding name.
If renaming an implemented Web service provider endpoint causes the .asmx file name to change, then any associated Web references and underlying proxy classes are deleted, which causes the corresponding Web service consumer endpoints to become unimplemented. You will need to reimplement the consumer endpoints to generate new Web references. If you are using source code control, you might also need to check in any affected files before reimplementing. To reimplement a Web service consumer endpoint, right-click the endpoint and choose Implement.
If renaming an implemented Web service provider endpoint causes the Web service name to change, proxy classes associated with Web references to the Web service will no longer match the service name. As a result, the application might not compile. To resolve this condition, fix those places in code that reference old service names.
To rename an application endpoint
Select the endpoint name on the diagram and edit the name.
Tip
If the endpoint label is not visible, right-click the endpoint, and choose Show Label. If you select a label, the associated endpoint is also highlighted. You can also move labels to a more convenient location on the diagram.
-or-
Select the endpoint on the diagram and edit the Name property in the Properties window.
Tip
If the Properties window is not visible, open it from the View menu by choosing Properties Window or pressing F4.
To rename a Web service provider endpoint in the Web Service Details window
Right-click the endpoint and choose Define Operations.
In the Web Service Details window, edit the endpoint name on the endpoint row.
See Also
Tasks
How to: Add Endpoints to Applications