Use wcf3.5 for restful Web Services and IIS deployment

Implementation:

The general practice is to add a series of features on the service interface, such as the operationcontract feature. However, to implement restful web services, you must add the [webget] feature. Because this feature can only be applied to get requests, if you want to use post requests, you must add the [webinvoke] feature.

For example:

[Operationcontract]
[Webget (uritemplate = "/")]
String helloworld ();

[Operationcontract]
[Webinvoke (uritemplate = "/", method = "Post")]
Result getdatausingdatacontract (compositetype composite );

After adding a service, use a service class to implement this interface. However, if this is the case, isn't it necessary to underestimate Microsoft?

Next, we need to declare servicehostfactory in this class. In this way, it can basically run in ASP. NET development server.

Test with a variety of testing tools, basically no problem.

 

It's too early to be happy. It can run correctly in ASP. NET development server, and does not mean it can also run correctly in IIS. If you do not do anything, once the service is set up on the server, you will find that the service has not been correctly displayed! In fact, configuring config in IIS means everything is fine. To remove the endpoint address, manually specify the endpoint address and modify it to allow others to specify and manage IIS, and IIS users do not need to set any wildcards in IIS, think about it !! For the rest, you do not need to intervene in anything. Just go to bed with peace of mind, this service will be able to work well under the management of IIS.

 

The final restful web service address will look like this: http: // *********/******. svc /***.