Free cookie consent management tool by TermsFeed Policy Generator

Changes between Version 6 and Version 7 of Documentation/DevelopmentCenter/Develop Services


Ignore:
Timestamp:
08/20/10 05:10:31 (12 years ago)
Author:
swagner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/DevelopmentCenter/Develop Services

    v6 v7  
    4848
    4949== Development ==
    50 After you have successfully completed all the steps described above, you are ready to start developing your own services and client applications. [attachment:"HeuristicLab Services Demo.zip" Attached to this page], you can find a Visual Studio 2010 solution file which contains two sample projects, one for a service and one for a client. These projects are a good starting point for developing custom HeuristicLab services. But before you are able to execute these two sample projects, some additional steps are necessary:
     50After you have successfully completed all the steps described above, you are ready to start developing your own services and client applications. [attachment:"HeuristicLabServicesDemo.zip" Attached to this page], you can find a Visual Studio 2010 solution file which contains two sample projects, one for a service (`HeuristicLab.Services.DemoService`) and one for a client (`HeuristicLab.DemoClient`). These projects are a good starting point for developing custom HeuristicLab services. But before you are able to execute these two sample projects, some additional steps are necessary:
    5151
    5252=== 1. Update Client Service Reference ===
    5353As we have created a new server certificate, we have to update the service reference in the client project:
    54  1. Open the `HeuristicLab Services Demo.sln` solution file.
     54 1. Open the `HeuristicLabServicesDemo.sln` solution file.
    5555 2. Update the service reference of the project `HeuristicLab.DemoClient`.
     56 3. Add the attribute `behaviorConfiguration="DefaultEndpointBehavior"` to the `endpoint` specification of the `client` section in the `app.config` file of the client project (please note that updating the service reference of the client overwrites the whole `client` section each time; therefore adding the behavior configuration has to be done everytime after updating the service reference). The `client` section should look like:
     57{{{#!xml
     58<client>
     59  <endpoint address="http://localhost:34825/Service.svc" binding="wsHttpBinding" behaviorConfiguration="DefaultEndpointBehavior"
     60            bindingConfiguration="WSHttpBinding_IService" contract="Services.DemoService.IService"
     61            name="WSHttpBinding_IService">
     62    <identity>
     63      <certificate encodedValue="AwAAAAEAAAAUAAAA ... B+3eQE6Y8inFygk=" />
     64    </identity>
     65  </endpoint>
     66</client>
     67}}}
    5668
    5769=== 2. Create Users and Roles ===
    58 You also have to add some users and roles for testing purposes. Users and roles can be administered using the `ASP.NET Web Site Administration Tool` which can be started in the solution explorer after clicking on the server project (have a close look at the tool bar of the solution explorer). Both sample projects require that there is a user called `Alice` who is member of the role `Everyone` and whose password is `YouWillNeverNow`.
     70You also have to add some users and roles for testing purposes. Users and roles can be administered using the `ASP.NET Web Site Administration Tool` which can be started in the solution explorer after clicking on the service project (have a close look at the tool bar of the solution explorer). Please note that the administration tool will not work, if the path of the service project contains any spaces or special characters. Both sample projects require that there is a user called `Alice` who is member of the role `Everyone` and whose password is `YouWillNeverKnow`.
    5971
    6072=== 3. Run the Services Demo ===