Hosting WCF Service 4.0 in IIS 7.5

Hi Everyone,

Today I want to show you what I did to get my WCF Service hosted on my development machine IIS (this could be your web server too). I am using VS 2010, .NET 4.0 framework, and IIS 7.5 in Windows 7 environment.

In this demonstration I am going to use my AlkitabWebService.svc found in this post: Silverlight 4 Simple Project Part 2 (WCF Service).

Step 1 - Enabling IIS + ASP.NET Registration
  • Click Start -> Control Panel -> Programs -> Programs and Features.
  • On the left tab, click Turn Windows Features on or off. Turn on the features below and click OK.


  • When you go to http://localhost , you will now see the IIS7 homepage.
  • Now go to a command prompt and run aspnet_regiis:


Step 2 - Publish the WCF service from VS 2010
  • Right-click the project and click Publish.
  • Choose 'File System' as Publish method, and type C:\inetpub\wwwroot\AlkitabWebService\


This will create a folder for your WCFService that you can refer to from IIS in the next step.

Step 3 - Create New Application in IIS
  • Go to your IIS Manager (can be accessed from Administrative Tools).
  • Right-click Default Web Site -> Add Application...
  • Enter in the Application Name and point the physical path to the folder that contains our published WCF service.


Step 4 - CrossDomain.xml and ClientAccessPolicy.xml
  • In order to be able to access your localhost in IIS, you need to implement a cross domain policy. I'm just going to make this simple. In your C:\inetpub\wwwroot folder, create a crossdomain.xml and clientaccesspolicy.xml files:

  • Crossdomain.xml

?
1
2
3
4
5
6
<?xml version="1.0"?>
 
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy> <allow-http-request-headers-from domain="*" headers="*"/>
 
</cross-domain-policy>


  • Clientaccesspolicy.xml
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
<?xml version="1.0" encoding="utf-8"?>
<access-policy>
    <cross-domain-access>
        <policy>
            <allow-from http-request-headers="SOAPAction" >
                <domain uri="https://*"/>
                <domain uri="http://*" />
            </allow-from>
            <grant-to>
                <resource path="/" include-subpaths="true"/>
            </grant-to>
        </policy>
    </cross-domain-access>
</access-policy>


Step 5 - Test your WCF Service
  • In IIS Manager, click the AlkitabWebService (alias).
  • On the right tab, click Browse*:80 to go to your http://localhost/AlkitabWebService/
  • You should get the view like this:


  • Clicking on AlkitabWebService.svc is our Service page. Yay!

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 anonymous access add attachments to list item

Image
Hi, Sometimes you want to enable anonymous access to be able to add a list item but at the same time attaching some documents. After good few hours playing around trying to make this work, turns out that we can achieve this functionality. The trick is to use RunWithElevatedPrivileges method for the file upload. We also want the file upload functionality to be available on the NewForm.aspx as it wouldn't make sense to put it in other forms as any user would be able to upload files to other records. The result will be something like this: When it is saved, the user is redirected to the display form: The close button then will take the user back to the homepage (or any page you desire) The steps: 1. Create an ascx control to host your file upload control in your project.  Put the below script in the ascx as well (credit to this post ): The code behind: 2. Create custom form template. You have to put the ascx in the CONTROLTEMPLATES folder of the ...
Read more

CRM Plugin - Parent and Child Pipeline

This concept tends to confuse people often - and I was no exception. I came across this problem when trying to create custom auto-numbering for one of my projects. Creating auto-number for Opportunity is easy. This is because the user creates opportunity straight from the home screen - thus the plugin runs on parent pipeline. However, it's a different story if you are dealing with Quote entity. Quote can be created in 2 ways, through the home screen OR the opportunity screen. If you create it from the latter, it will run on the child pipeline and you will find that your plugin will not work. Registering it as a child pipeline is easy, but CRM makes it harder since you can't use ICRMService. Instead, you have to create CRMService manually by using this piece of code: Not only that, with the child plugin you can't use Query expression to fetch other entities in your code unless you register it as ASYNCHRONOUS plugin. Mark Kovalcson in his blog found out that: A C...
Read more