2014-01-27, 03:36 AM
Ok, I'll admit it. I seem to have gotten stuck drinking MSFT cool-aid for too many years. The transition from SOAP to WCF was pretty reasonable, but this JSON stuff that's all the rage with the cool kids has me a bit mystified. I can fully appreciate you wanting to use this system as a competing standard to WCF because it removes that dependency on MSFT, so please don't take this as a rant against it. I'm willing to work with it
Can somebody help a poor old MSFT guy with your new fancy Swagger documented API? Can I somehow generate all the classes from the API; and make calls to the API with the old school things I am used to, or do I really need to invoke the HTTP methods and make all the calls myself, passing everything correctly. You know, like we used to do with the WSDL generator?
The interwebs is full of people talking about how to use the Swagger system to document code, but nobody seems to have a guide for generating the classes for your client (particularly when it comes to .net clients).
Hint: Maybe the project itself already has the objects I'm looking for and they could be provided
Thanks!
Can somebody help a poor old MSFT guy with your new fancy Swagger documented API? Can I somehow generate all the classes from the API; and make calls to the API with the old school things I am used to, or do I really need to invoke the HTTP methods and make all the calls myself, passing everything correctly. You know, like we used to do with the WSDL generator?
The interwebs is full of people talking about how to use the Swagger system to document code, but nobody seems to have a guide for generating the classes for your client (particularly when it comes to .net clients).
Hint: Maybe the project itself already has the objects I'm looking for and they could be provided
Thanks!