Lab Manual Visual Studio Team Architect Edition

Transcription

1 Hands-On Lab Lab Manual Visual Studio Team Architect Edition ARC02: Using the Application Designer to design Your Web Service Architecture in Microsoft Visual Studio 2005 Page 1

2 Please do not remove this manual from the lab Information in this document is subject to change without notice. The example companies, organizations, products, people, and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarked, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property Microsoft Corporation. All rights reserved. Microsoft, Visual Basic, Visual C#, Visual Studio, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. Other product and company names herein may be the trademarks of their respective owners. Page 2

3 Page 3

4 Contents ARC02: USING THE APPLICATION DESIGNER TO DESIGN YOUR WEB SERVICE ARCHITECTURE IN MICROSOFT VISUAL STUDIO Lab Objective...1 Exercise Using the Application Designer to Design Your Web Service...2 Task 0 Select the Solution...2 Task 1 Design a service-oriented system...3 Task 2 Implement a Web Service...7 Task 3 Manage the Exposed WSDL file...8 Task 4 Contract (or WSDL) First Design of a Web Service...10 Task 5 Web Service Substitution...12 Task 6 Separating out Web service client proxy behavior to a Class Library...14 Task 7 Using the Class Designer to design your Web Service...16 Page 4

5 Page 5

6 ARC02: Using the Application Designer to Design Your Web Service Architecture in Microsoft Visual Studio 2005 Lab Objective Estimated time to complete this lab: 30 minutes For the purpose of this walkthrough, you will only use the Application Designer. The Application Designer is a part of the Distributed System Designers that will be shipped in Microsoft Visual Studio Team Edition for Software Architects. The Distributed System Designers consists of the following designers: 1. The Application Designer (AD) helps application architects and developers design, construct, and configure services and the applications that consume these services. 2. The System Designer (SD) allows application architects to compose and configure systems for deployment independent of the development configuration used during design. 3. The Logical Datacenter Designer (LDD) allows infrastructure architects and operations teams to describe datacenter architectures including the configuration constraints, logical topology, and policies to be imposed on applications. 4. The Deployment Designer (DD) helps developers and operations teams validate applications against their datacenter architecture and its constraints, prior to deployment. The purpose of this lab is to illustrate the benefits of the Application Designer in designing serviceoriented web service architectures. This lab will not illustrate the end-to-end value of the Distributed System Designers for application architects, IT professionals, and developers. That is covered in ARC01 Using the Distributed System Designers to Visually Design and Validate Service- Oriented Systems in Microsoft Visual Studio 2005 Related Labs: ARC01: Using the Distributed System Designers to Visually Design and Validate Service- Oriented Systems in Microsoft Visual Studio 2005 ARC03: Using the Logical Datacenter Designer for Configuration and Deployment in Microsoft Visual Studio 2005 Page 1

7 Exercise Using the Application Designer to Design Your Web Service This hands-on lab explores how the Visual Studio 2005 Application Designer makes it easier for application architects and developers to design and develop complex multi-node Web service-based systems. In this lab, you will: Design a Web service that adheres to a pre-defined Web service description language (WSDL) contract (WSDL provides a vendor neutral specification of a Web service) Learn how to develop a Web service, configure the automatically generated WSDL file, and define the format of the SOAP messages used for communication. See how, by using the WSDL binding name and namespace properties to type the behavior of a Web service, the tools can use this information to provide basic type checking when you connect Web services. These and other features support developing substitutable Web services. See how the tools support the use of hand-written proxy classes, which are useful if you wish to encapsulate client-side message processing in the proxy. See how the tools visualize Web service connections made from a class library that could be deep within the structure of your application. See how to access the Class Designer to help create the detailed implementation for the Web service. Task 0 Select the Solution Task 1 and Task 2 are similar to lab ARC01: Using the Distributed System Designers to Visually Design and Validate Service-Oriented Systems in Microsoft Visual Studio Login to Microsoft Windows using the following user name and password: administrator/pass@word1 Open Visual Studio 2005 Beta 2 by clicking on the Resource Management shortcut on the desktop. If required, choose a profile and click OK. Visual Studio 2005 Beta 2 opens. On the File menu, point to Open and click Project/Solution. o o Select the ResourceManagement project. Select ResourceManagement.sln. Page 2

8 Click Open. Double-click on the ResourceManagement.ad file in Solution Explorer (if Solution Explorer is not visible, on the View menu, choose Solution Explorer, or alternatively, press Ctrl+Alt+L) The Application Designer displays an application diagram with the abbreviation, AD, on the document tab and Application Designer tools appear in the Toolbox and on the toolbar. The diagram displays several existing application definitions and external applications. Task 1 Design a service-oriented system The Application Designer provides a design surface for defining applications, describing the services these applications offer and describing the connections between these applications. In this lab, applications will communicate via Web services. With the Application Designer, architects can define application specifications that will eventually be implemented. They can experiment with each application s settings and design. If required, the Application Designer can be used to generate code skeletons that developers must fully implement. Once an application is generated, the Application Designer keeps the design and code synchronized. It is also possible to reverse engineer the design from existing code to visualize the connections that exist among applications in your solution. In this lab, we ll start by examining some existing application definitions on the application diagram. The first definition we ll examine is for a database. On the diagram, notice the definition of a database called ProjectsDB. This definition was created from the ExternalDatabase prototype in the Toolbox and will be used to document a connection to an existing database. On the diagram, notice the existing definition of an ASP.NET application called ProjectService on the diagram surface. This definition was created from the ASP.NETWebService prototype in the Toolbox. Select the ProjectService application and push F4 to bring up the Properties window. In the Properties window, notice that the Language property is set to Visual Basic. Note: If you would like to use Microsoft Visual C# instead of Microsoft Visual Basic, please change the Language property for the ProjectService application to Visual C#. Next, notice the connection between ProjectsDB and ProjectService on the diagram: On the ProjectService application, select the database consumer endpoint (the small hollow white hexagon, which is connected to ProjectsDB). Page 3

9 In the Properties window, notice the Connection String property. The Connection String setting will be generated in the Web.config file of the ProjectService application when it is implemented. To define Web service operations, click the Web service provider endpoint (small solid blue circle) also called ProjectService on the ProjectService application definition. The Web Service Details window displays at the bottom of the screen (Note: if the Web Service Details window is not visible, right-click the Web service provider endpoint and select Define Operations, alternatively go to the View menu, select Other Windows and Web Service Details). Notice that an operation already exists on the Web service provider endpoint called GetProjects. In the <add operation> field, add another operation called AssignEmployeeToProject to the Web service. The Modifier and Summary field should be left empty. Visual C# Change the value in the Type column to bool and push Enter Visual Basic Change the value in the Type to Boolean (type Boolean under the Type heading) and push Enter Next, add parameters to the AssignEmployeeToProject operation. To add parameters to an operation, expand the operation node in the Web Service Details window and parameter fields will appear. Click <add parameter> to add parameters named employeeid and projectid with int type (in C#) or Integer type (in VB) The Web Service Details window will look like Figure 1.2 after you make your modifications: Figure 1.2a (C#): The Web Service Details window Figure 1.2b (VB): The Web Service Details window Page 4

10 Next, notice the External Web Service named CompanyDirectory on the design surface. The External Web Service has been created on the basis of a WSDL file at the following location: This can be seen by selecting the External Web Service, pushing F4 to bring up the Properties window, and viewing the WSDL Location property. To examine the operations provided by the External Web Service, click on the DirectoryService endpoint (small solid blue circle), and then look at the Web Service Details window. (Note: if the Web Service Details window is not visible, go to the View menu, select Other Windows and Web Service Details). The Web Service Details window shows that the External Web Service exposes the following operations: GetEmployee, and GetAvailableEmployees. Note: If the External Web Service did not comply to the WS-I ( Basic Profile 1.1, the industry standard for interoperability compliance, an error would have appeared in the Error list to inform you that the External Web Service does not comply to the profile. The design surface will support the use of the non-compliant External Web Services for legacy reasons. However, it is highly recommended that only WS-I Basic Profile 1.1 compliant Web services are created and used. Add an ASP.NET Web application by dragging the ASP.NETWebApplication application prototype from the Toolbox to the diagram. Place this on the top of the diagram. An application definition named WebApplication1 is added to the design surface. Note: If you would like to use Visual C# instead of Visual Basic, change the Language property for the WebApplication1 application to Visual C#. Tip (Optional): Application definitions that appear on the toolbox can be customized by creating a custom prototype. This prototype will display whenever you open the Application Designer as it is a function of the designer and not the solution that was open when you created it. One scenario for creating a custom prototype is if you want to use a language other than Visual Basic as your default language for ASP.NETWebApplications. To accomplish this, create a custom ASP.NETWebApplication prototype that uses your preferred language. Change the Language property for the WebApplication1 ASP.NETWebApplication to Visual C#. On the Application Designer, right-click on WebApplication1 and choose Add to Toolbox. Page 5

11 Under Name, enter C#ASP.NETWebApplication and click OK. The Save File dialog box appears. The file is saved as an.adprototype, meaning that it is an application prototype for the Application Designer. Click Save. The toolbox should now have a custom prototype called C#ASP.NETWebApplication. You can now use the C#ASP.NETWebApplication to create ASP.NET applications where the language is set to Visual C# by default. Right-click WebApplication1 and choose Properties. In the Properties window, rename the application from its default name of WebApplication1 to ResourceManagementWeb. Resize the application so that the complete name is displayed in the application on the diagram. (Alternatively, you can rename the application directly on the diagram by double-clicking on the name of the application) Next, connect the ResourceManagementWeb application to the ProjectService application by: Moving the pointer over the ProjectService Web service endpoint (small solid blue circle) on ProjectService, pressing the Alt key, and dragging a connection to ResourceManagementWeb. In a similar fashion, connect the DirectoryService Web service endpoint (small solid blue circle) to ResourceManagementWeb. Rearrange your diagram to resemble the diagram shown in Figure 1.4: Figure 1.4 Application Diagram Page 6

12 Save the solution by choosing Save All from the File menu. Task 2 Implement a Web Service You will now use the designer to create a skeleton implementation for the ProjectService application. Developers can later populate this skeleton code to implement the project. Right-click the diagram and click Implement All Applications. The Confirm Application Implementation dialog appears. Click OK, and Visual Studio will create a Web service project named ProjectService (this step may take a few minutes) and the Web application project named ResourceManagementWeb Note: You may get a Synchronization Warning dialog. You can safely dismiss this dialog by clicking Close. After implementation is complete, your Solution Explorer should look similar to the following screenshot: Double click the ProjectService.cs or ProjectService.vb file in Solution Explorer (depending on your implementation language) to display it in the code editor. Note that the operations you defined in the Web Service Details window are now reflected in code. Next we will show how the Application Designer is kept synchronized with changes in the code. Page 7

13 Visual C#: In the code view, update the GetProjects method to that shown below: Visual Basic: public System.Xml.XmlDocument GetProjects() { return new System.Xml.XmlDocument(); } In the code view, update the GetProjects method to that shown below: Public Function GetProjects() As System.Xml.XmlDocument End Function Return New System.Xml.XmlDocument() Switch back to the Application Designer by clicking the ResourceManagement.ad tab at the top of the editor window. Click the ProjectService endpoint and then display the Web Service Details window by going to the View menu, selecting Other Windows and clicking Web Service Details. Note the changes made to the return type of the GetProjects operation are reflected in the designer; the GetProjects operation s return type is now correctly reported as System.Xml.XmlDocument. Note: You will see only XmlDocument unless you click in the Type field, at which point you will see the fully qualified name. Save the solution by choosing Save All from the File menu. Task 3 Manage the Exposed WSDL file WSDL is an XML based language that is used to describe a Web service's behavior as endpoint(s) capable of exchanging messages. A WSDL document, therefore, defines the Web service contract that describes the messages exchange protocol required to communicate between a Web service provider and a consumer endpoint..net-based.asmx Web services automatically generate WSDL documents to describe the capabilities of the Web service at that location. You can control WSDL file generation through properties for the endpoint and operation in the Application Designer. Detailed property descriptions of each WSDL property will help you understand the impact on the generated WSDL of setting each property. Page 8

14 In Solution Explorer, right-click the ProjectService.asmx file and choose View in Browser. (HINT: If Solution Explorer is not visible, press Ctrl+Alt+L) If prompted with a dialog to save, click OK. The test page for the Web service will appear. At the end of the sentence: For a formal definition, please review the Service Description., click the Service Description link. The WSDL file for the Web service will appear. Note that the target namespace is in the schema tag. Close the browser and return to the ResourceManagement.ad application diagram in Application Designer. On ProjectService, select the ProjectService endpoint. In the Properties window (HINT: Press F4) change the WSDL Service Namespace property to This property is located under the WSDL heading in the Properties window. View the WSDL file for ProjectService.asmx again (steps above) Note that the target namespace is now in the schema tag. The Application Designer also manages the various artifact/attribute names for a Web service, managing and propagating changes you make on the design surface or the property grid to all the related artifacts in the project and code. Change the name of the ProjectService endpoint to PRService. There might be a slight delay while name propagation occurs. Bring up the Properties window. Note that the following have now changed: o o o Class Name = PRService WSDL Service Name = PRService WSDL Binding Name = PRService In the Solution Explorer notice that the following has changed o o The class file name in the App_Code folder = PRService The.asmx file name = PRService Change the.asmx file name back to ProjectService.asmx in Solution Explorer Change the endpoint name to ProjectResourceService. Notice that the name no longer propagates to the.asmx file name because you have broken the propagation links by manually changing the name of one of the dependent artifacts. Close the ResourceManagement.ad application diagram. If prompted to save, select Yes. Page 9

15 In Solution Explorer, right-click the ProjectService project and choose Add New Item -> Web Service. If Solution Explorer is not visible, press Ctrl+Alt+L. Name the Web service AdminService.asmx. The AdminService Web service class file should appear in Solution Explorer. Open the class file and update the WebService attribute to one of the following: Visual C# [WebService(Name="Administration", Namespace=" Visual Basic <WebService(name:="Administration", Namespace:=" _ Reopen the ResourceManagement.ad application diagram. Notice that a new endpoint on ProjectService has been created. The name of the endpoint has been derived from the WSDL Service name, Administration. Save the solution by choosing Save All from the File menu. Task 4 Contract (or WSDL) First Design of a Web Service One methodology for designing and developing Web services for heterogeneous systems is to design the XML messages transported over the wire, and from these create WSDL contracts that describe the exposed behavior of the Web services, prior to implementation. This approach makes good sense if your Web services will be used by third parties and where it is important for you to agree on the contract. Once the XML messages and a WSDL contract have been designed, the Application Designer can be used to create a Web service implementation that conforms to that WSDL. During this task the architecture of the ResourceManagement System will be changed to add connections to an external vendor s Web service. The Message Broker pattern will be used between ResourceManager and the various resources available for a particular project. The message broker will pull information together and make it available as a consolidated whole. From the Toolbox, drag an ExternalWebService to the ResourceManagement.ad application diagram. A dialog will appear prompting you for the location of the Web Service. Type the following URL in the URL text box and click Go: Page 10

16 Click Add Reference Rename the VendorService external Web service application to VendorDirectory From the Toolbox, drag an ASP.NETWebApplication (or C#ASP.NETWebApplication if you created a custom prototype) to the application diagram. Change the name of the ASP.NET Web application to ConsolidatedResources. This will be the message broker. Move the pointer over the DirectoryService Web service endpoint (small solid blue circle) on CompanyDirectory, press the Alt key, and drag a connection to ConsolidatedResources. Click on the consumer endpoint (small hollow circle) created on ConsolidateResources and rename it to CompanyDirectoryService in the Properties window (press F4). Move the pointer over the VendorService Web service endpoint (small solid blue circle) on VendorDirectory, press the Alt key, and drag a connection to ConsolidatedResources. ConsolidatedResources should now adhere to the same WSDL contract that DirectoryService on CompanyDirectory implemented. Doing this will minimize the effect of this change on ResourceManagementWeb once reconnected. Right-click the ConsolidatedResources Web application and choose Create Web Service Endpoints From WSDL. In the Add Web Reference dialog box, enter the following URL: and click Add Reference. A new provider endpoint called DirectoryService is created on ConsolidatedResources. Right-click the DirectoryService endpoint on ConsolidatedResources and choose Define Operations to view the Web Service Details window. Notice that the endpoint s operations match those defined on the DirectoryService endpoint on the CompanyDirectory application. Right-click on ConsolidatedResources and select Implement Application. When prompted by a Confirm Application Implementation dialog, click OK. Right-click the DirectoryService endpoint on the ConsolidatedResources application and choose Define Operations. In the Web Service Details window, right-click on the operation GetEmployee and choose View Code - Resource. Notice that types used in messages specified in the contract have been implemented as serializable classes and these classes are referenced in the operation/web method definitions. Save the solution by choosing Save All from the File menu. Rearrange your diagram and your connections to resemble the following diagram. You can redraw connections by right-clicking a connection and choosing Redraw Connection. To view the entire diagram, change the zoom level from the toolbar. Page 11

17 Task 5 Web Service Substitution There are two interesting and distinct locations associated with Web services: the location of the WSDL contract that defines the Web service, and which will be used to create a client proxy, and the location of the Web service itself at which the operations can be invoked. Both of these locations are likely to change when you finally deploy the application. However, the WSDL used to define the behavior should not change between development and deployment. Furthermore, treating these locations distinctly allows you to define a client proxy from a WSDL file at a common location and then test the application with any number of Web services that implement that contract but which are accessed at different URLs.. In Visual Studio 2005, Web references all have a default Web service location setting generated in the configuration file. This setting can be easily modified at deployment time to connect to a different location. This concept allows you to easily substitute Web service providers without having the update/change the Web reference being used to consume the Web service. This task will take you through the process of substituting one web service for another on the diagram without having to change the consumer application. In the Solution Explorer (Ctrl+Alt+L), open the ResourceManagerWeb project and navigate to the App_WebReferences folder. Expand the directory and notice the WSDL file called DirectoryService.wsdl. This corresponds to the DirectoryService consumer endpoint. Page 12

18 From the ResourceManagerWeb project, open the Web.config file. The following appsettings entry contains the location of the Web service: <add key="resourcemanagementweb.webserviceproxies.directoryservice" value=" Switch back to the Application Designer. Select the connection (HINT: Not the endpoint) between ResourceManagementWeb and CompanyDirectory. Press the Delete key to delete the connection from the application diagram. Notice that the consumer endpoint on ResourceManagerWeb is not deleted. If you expand the ResourceManagerWeb project in the Solution Explorer, you will notice that the Web reference that corresponds to the consumer endpoint is also not deleted. In the Toolbox, select the Connection tool. Drag the tool from the DirectoryService consumer endpoint and move it over the ProjectResourceService Web service provider endpoint. A warning tooltip appears that states that the binding name and binding namespace on the consumer endpoint do not match those set on the provider endpoint. In the WSDL contract, the binding element defines the concrete format of the messages by detailing the actual format of the messages, the protocol used during the interactions, and the network transport used to exchange the messages. Therefore, as a best practice, the binding name and namespace of a Web service define the behavior of the Web service endpoint. Consequently, when there is a binding name and namespace mismatch between a provider and consumer endpoint, the Application Designer displays a warning. You can still make the connection, if required, as this best practice is not enforced by the ASP.NET infrastructure. Move the Connection tool over the DirectoryService Web service endpoint on ConsolidatedResources. Notice that there is no warning as the Binding name and namespace match. Make the connection. You are prompted with the following dialog: If the default option is selected, the Web reference will be updated according to the WSDL location specified by the DirectoryService Web service provider endpoint on the ConsolidateResources application. In this scenario, we do not want to update the Web reference. Page 13

19 Select the Connect only option in the Reconnected Web Service Endpoints dialog box. A warning icon appears on the consumer endpoint. When moving the pointer over the consumer endpoint, a tooltip indicates that the WSDL location used to define the Web service consumer endpoint is different from the WSDL location specified by the Web service provider endpoint. Switch back to the Web.Config for ResourceManagerWeb. Notice that the Web service location has changed. Arrange your diagram so that it looks like the following: Save the solution by choosing Save All from the File menu. Task 6 Separating out Web service client proxy behavior to a Class Library Class libraries and the behavior they offer in most cases are designed for in process tightly coupled communications that share data and behavior and inherently share types between them. This provides for efficient processing. While Visual Studio automates the creation of Web service proxy classes as part of creating a Web reference and these will in most cases be all you ever need to use, there are occasions when it may be considered useful to write custom proxies. Encapsulating client-side message processing within the proxy is one such scenario. The following task is going to combine both the use of Web service connections made from within a referenced class library and the use of a custom proxy. Page 14

20 1. In the Solution Explorer (Ctrl+Alt+L), right-click on the solution node and choose Add New Project. Select the Visual Basic or Visual C# node and then Windows in the project types list. Then select Class Library from the templates list. Name the class library ResourceClientClassLibrary and click OK. 2. The class file opens. In Solution Explorer, expand the ResourceClientClassLibrary project to view the Class1.vb or Class1.cs file. In the class file, rename the Class1 class to ProjectResourceProxy. This is where you will add your proxy class code. 3. In the Solution Explorer, right-click on the ResourceClientClassLibrary project and choose Properties. Select the Settings tab and add the following setting: a. Set the Name value to the fully qualified Web service client proxy class name: ResourceClientClassLibrary_ProjectResourceProxy b. Set the Type value to indicate that this is a client Web service proxy setting: (Web Service URL) c. Leave the Scope value set to Application. d. Set the Value to the URL where the Web service client proxy class will consume from: 4. In Solution Explorer, right-click the ResourceClientClassLibrary project and choose Build to build the class library. 5. From the class library s App.config file, copy the appropriate entries from the configsections and applicationsettings sections and paste them into the appropriate sections of the ResourceManagementWeb s Web.config file as follows: a. The configsections section should be pasted following the <configuration> tag at the top of the config file and preceding the <appsettings> tag: <configsections> <sectiongroup name="applicationsettings" type="system.configuration.applicationsettingsgroup, System, Version= , Culture=neutral, PublicKeyToken=b77a5c561934e089" > <section name="resourceclientclasslibrary.settings" type="system.configuration.clientsettingssection, System, Version= , Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </sectiongroup> </configsections> b. The following should be pasted following the appsettings section: <applicationsettings> <ResourceClientClassLibrary.Settings> <setting name="resourceclientclasslibrary_projectresourceproxy" serializeas="string"> <value> </setting> </ResourceClientClassLibrary.Settings> </applicationsettings> Page 15

21 6. From the ResourceManagementWeb project, add a project reference to the class library. (HINT: Right-click on the ResourceManagementWeb project and choose Add Reference. In the Projects tab, select ResourceClientClassLibrary and click OK.) 7. On the application diagram, a consumer endpoint called ProjectResourceProxy should appear ResourceManagementWeb. This endpoint visualizes the custom Web service client proxy code that you wrote in the class library. 8. Delete the ProjectResourceService Web service consumer endpoint from ResourceManagementWeb. Task 7 Using the Class Designer to design your Web Service This task illustrates the benefits of integration with the new class diagramming tool available in Visual Studio The class diagramming tool, known as Class Designer, provides visualization, class building, refactoring, and documenting features to help architects and developers work with class structures. The Class Designer is covered in more detail in the following Hands-On Lab, DEV029: Understand, Design, Refactor and Document Code using the new Class Designer tool in Visual Studio In this task we will replace the primitive types in the AssignEmployeeToProject operation with complex types which we will design with the Class Designer. We ll also see how the Class Designer can be used in the design of the Web service class. Right-click on the ProjectResourceService Web service provider endpoint on ProjectService ASP.NET application and choose Define Operations. This will bring up the Web Service Details window. Expand the AssignEmployeeToProject operation. Delete the parameters by selecting each entire parameter row in the AssignEmployeeToProject operation and pressing the Delete key. Add a parameter named EmployeeProjectMapping with type EmployeeProject and press Enter. Right-click the EmployeeProjectMapping parameter and choose Define EmployeeProject in Current Project. When asked to view in the Class Designer, choose Yes. (HINT: If the class diagram appears blank, make sure zoom is set to 100% in the toolbar.) Right-click the EmployeeProject class shape on the diagram and choose Class Details Page 16

22 Add the following properties: Visual C# o projectid with int type o employeeid with int type Visual Basic o projectid with Integer type o employeeid with Integer type Select the ResourceManagement.ad application diagram. Right-click the ProjectResourceService endpoint and choose View in Class Diagram - ProjectResourceService. Expand the ProjectResourceService class. From the Toolbox in Class Designer, select Association and drag an association from ProjectResourceService to EmployeeProject. By creating an association, you have created an EmployeeProject member type for ProjectResourceService. The Class Designer allows you to view this relationship as a simple property or as an association. The following illustration shows this relationship as an association. If you right-click the association line and choose Show as Property, you will see the EmployeeProject member type represented as a property of the ProjectResourceService type. This completes the ARC02: Using the Application Designer to Design Your Web Service Architecture in Microsoft Visual Studio 2005 walkthrough. Page 17