IIS Hosting in windows communication foundation service

Question

0.00/5 (No votes)

See more:

Hai to all,

I am developing the sample wcf service for IIS Hosting.In the web config file in the endpoint whether i have to use the address 'http://localhost//IISService/Myservice.svc' or my file folder like'c:/documentsettings/visualstudio2008/IISService/Myservice.svc.Please clear my doubt

Posted 24-Feb-11 17:44pm

sridharan28

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

*dan!sh* · Answer 1 · 2011-02-24T21:57:00

Solution 1

You should be using the URL in the client configuration for the endpoint.

Posted 24-Feb-11 21:57pm

dan!sh

Dylan Morley · Answer 2 · 2011-02-24T22:30:00

A config could read something like this. As d@nish mentions, you use the URL rather than the file system path to resolve the service endpoint.

XML

<system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="BasicHttpBinding_MyApplication" closeTimeout="00:01:00"
            openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
            allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
            maxBufferSize="1000000" maxBufferPoolSize="524288" maxReceivedMessageSize="1000000"
            messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
            useDefaultWebProxy="true">
          <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
              maxBytesPerRead="4096" maxNameTableCharCount="16384" />
          <security mode="None">
            <transport clientCredentialType="Windows" proxyCredentialType="None" realm="" />
            <message clientCredentialType="UserName" algorithmSuite="Default" />
          </security>
        </binding>
      </basicHttpBinding>
    </bindings>
    <client>
      <endpoint address="http://localhost/YourVirtualDirectory/SomeService.svc"
          binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ MyApplication "
          contract="ISomeInterface" name="BasicHttpBinding_ISomeInterface " />
    </client>
</system.serviceModel>

If you right click on your service in Visual Studio & choose 'View In Browser', it'll open the service and show you some syntax for creating a client side proxy.

svcutil.exe http://localhost/YourVirtualDirectory/SomeService.svc?wsdl

If you open your visual studio command prompt & run that command, it'll create a proxy class for your service & it will also create a service config file for you.