I'm looking for a documentation tool for REST services created using the 'WCF REST Service Template 40' and came across Autodocs (http://autodocs.codeplex.com/), however I'm not sure if they'll work together....
Anyone who has made it work or any suggestions to another tool to use for documentation (It's rather important that's it's the REST services which gets documented, and not the C# API)
TIA
Søren
Working with Autodocs for any length of time it becomes pretty obvious that the support is not there for the project yet. Its just too young. I ran into a few errors that stopped me from pursuing it after I found the documentation help methods integrated into WCF 4.0
The post explaining my error:
http://social.msdn.microsoft.com/Forums/eu/wcf/thread/b196a05f-2d28-449e-9620-a74f939a625f
WCF Web HTTP Service Help Page
http://msdn.microsoft.com/en-us/library/ee230442.aspx
Hope that helps you.
Related
I have a requirement to access a wcf webservice from my node server.I came across a module called wcf.js which was rated for that purpose.But am confused with the part of message can anyone give me an explanation as how to code using that module will be really helpful.
The codeproject article at http://www.codeproject.com/Articles/379389/Wcf-js-Call-WCF-web-services-from-Node-js has some examples of how to call a WCF service using that package. And the project's page on GitHub also has some documentation.
In the GitHub project you can also find some examples, and the tests for this project (and for any project, in general) are always a good starting point to see how one would use a framework.
Masters,
I've few past developed VB6 components that are heavily used in our most of the applications
Now, we want to consume same components for newly developing Web API project.
But, as per this post ,
http://www.west-wind.com/weblog/posts/2012/Sep/18/Creating-STA-COM-compatible-ASPNET-Applications
We found strike on Asp.net Web API it might due to we don't have any page in Web API project.
Please tell me correct workaround achieve this.
Thanks in advance.
I would suggesting looking into the StaTaskScheduler http://blogs.msdn.com/b/pfxteam/archive/2010/04/07/9990421.aspx
I've been trying to figure out how to host a SOAP WCF Service in IIS and protect it by ACS, but I keep running into problems with every single example I can find. For instance, none of the standard ACS samples (http://acs.codeplex.com) show how to do this. Instead, the closest example shows how to self-host a WCF service but does not show how to host the service in IIS. Other examples work fine but are either REST-oriented, or inexplicable or simply uncompileable. I have researched this a lot but I am clearly getting nowhere. What I really need is a detailed walthrough that works end-to-end. Any help in this regard would be greatly appreciated. Thanks....
AFAIK it boils down to getting the web.config correct. This is explained in the e-book http://www.microsoft.com/en-us/download/details.aspx?id=28362 on page 145 and following. You need to correctly configure the ws2007FederationHttpBinding on your web-service.
I am going to need a web service that receives a string via HTTP POST and processes it without any response to the client. However, since I'm not the one making the client (which will be cell phones) I am unable to use a generated client class to consume the service. The service would also need to be self hosted in a regular Windows service, if that matters.
As I'm not too experienced with web services nor WCF, I am frankly unsure if I can or should use WCF for this, but as it's the only type of web service I'm at least a little familiar with I figured it would be great to start out with one if at all possible.
I've been googling around quite a bit but haven't been able to find any good references to this, so I'd also be very grateful if someone has a link lying around to someplace that discusses it.
I think you need WCF Restful service with one way operation. Following link might help you:
A Developer's Guide to the WCF REST Starter Kit,
What is the difference between WCF and WSE2.0 webservices when it comes to implementation of basic httpbinding. Can anyone point out what may be the subtle differnces when it come sto use the same protocol but using different technology.
Not sure if this is what you're looking for but I've only run into a difference once. I generated wcf proxies against a very old asmx webservice and ran into serialization errors on certain operations. When I regenerated the code using a "legacy" web reference everything worked fine.
A very good article describing this is here.
Also the various wcf bindings are explained here
hope this helps.