Click here to Skip to main content
15,880,405 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
1. i created a REST webservice as explained in the article
XML
<a href="http://www.codeproject.com/KB/webservices/REST_Web_Service.aspx">.NET 2.0 REST Service</a>[<a href="http://www.codeproject.com/KB/webservices/REST_Web_Service.aspx" target="_blank" title="New Window">^</a>]

2. When i try to access the service using the URL referring to ASP.NEt debugger server on local host, it works perfectly all right.

3. Now its time for me to publish on the IIS server and i did so just like how we do for normal websites.

4. However when i try to access using the url referring to the IIS server, it doesnt return the result, rather it says page doesnt exist.

Please note that i went though the comments/suggestions provided below the article.
Posted
Updated 1-Apr-11 9:34am
v2
Comments
Monjurul Habib 1-Apr-11 15:22pm    
need more clarification regarding your problem.
Member 3378549 1-Apr-11 15:30pm    
1. i created a REST webservice as explained in the article referred
2. When i try to access the service using the URL referring to ASP.NEt debugger server on local host, it works perfectly all right.
3. Now its time for me to publish on the IIS server and i did so just like how we do for normal websites.
4. However when i try to access using the url referring to the IIS server, it doesnt return the result, rather it says page doesnt exist.

As that article uses custom handlers you may need to map those handlers. Because IIS or ASP.Net processes may not understand such file extension requests.

Go through this link http://support.microsoft.com/kb/308001[^]

Refer to deploy the handler section. Note this method differ for different versions of IIS.If you using windows 7 the IIS manager has a icon link for handler mappings.

Rest of the things are similar as Sandeep Mewara said
 
Share this answer
 
Comments
Member 3378549 2-Apr-11 1:18am    
thanks Albin, that URL helped as the issue was all about setting up the handlers and the way it was explained in the original article didnt work out. thx again, u made my day..
Albin Abel 2-Apr-11 1:38am    
You are welcome
1. Add new virtual folder for existing website or add new website, binded to webservice phisical folder /RESTService in project.
2. Bind this site/folder to new or existing Application Pool (make sure, pool configured to support appropriate ASP.NET version, 2.0 in this case)
3. Chenge server form Default (which is Development server) to custom server with appropriate URL.
4. Check code for hardcoded URLs, some of them may have to be changed appropriatelly.

I got the above information from your mentioned link(Comments and Discussions part).Did yo read those comments?


I hope the above information will be helpful. If you have more concerns, please let me know.
 
Share this answer
 
Comments
Member 3378549 1-Apr-11 15:23pm    
thanks for your effort, However i went through theose commnets before posting this question, those didnt help me.
Though you say you followed the article, looks like you missed the first thread in the article forum at the bottom. It discusses the exact thing: http://www.codeproject.com/Messages/2869485/Re-How-to-implement-this-service.aspx[^]

Further, hosting a website or a webservice is similar thing. For hosting the Webservice/website:

1. In IIS7: Deploying ASP.NET Websites on IIS 7.0 [^]
2. In IIS6: Deployment of a Website on IIS[^]
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900