Re:Why .NET?
by okhudeira on Friday December 11, 2015 @06:24PM
(#10720873)
SOAP and WCF is a very scary thing. We're in the financial industry and many of the systems we integrate with use .NET and SOAP/WCF.
Although Visual Studio does all the heavy lifting for us via 'Add Service Reference', the sheer amount of boilerplate code generated when integrating a SOAP service is terrifying and bloated. We hope to migrate to ASP.NET 5 but we're not sure how well connectivity with SOAP services will be supported. One of our partners actually requires us to host our own SOAP service based on a spec they provide.
Although Visual Studio does all the heavy lifting for us via 'Add Service Reference', the sheer amount of boilerplate code generated when integrating a SOAP service is terrifying and bloated. We hope to migrate to ASP.NET 5 but we're not sure how well connectivity with SOAP services will be supported. One of our partners actually requires us to host our own SOAP service based on a spec they provide.
However, for our own APIs we use ASP.NET Web API and build REST/JSON APIs as highlighted in the stack page (http://engineering.gopangea.com/stack).