Fernando D. Bozzo wrote on 2015-06-10: > Ok, to continue with this matter, I can confirm that any COM+ component can > be automatically published as a web-service without the need of the Soap > Toolkit on Windows Server 2003. > > The bad news is that apparently Microsoft decided to quit this good thing > to replace it with WCF. I hate them :_( > > https://social.msdn.microsoft.com/Forums/sharepoint/en-US/c37ac0cb-96c7-405e -8acc-64061afa2e5f/com-as-xml-web-services-on-windows-7-uses-soap-setting?fo rum=windowsgeneraldevelopmentissues > >
Fernando, COM+ is difficult to test and debug. Not impossible. The fact that it is difficult, has left many COM+ objects with security problems. COM+ is not going away anytime soon. Using them in IIS is not something I want to repeat. Though I do maintain one in house. I have written one process using WCF that uses VFP9 COM DLL to work with the VFP tables. I later changed the process to use WebAPI that required a change to the VFP9 COM DLL. I'm still learning. I like WebAPI, the calling code can request a return type of XML and it returns it. It will return JSON by default. The easiest way to debug all of that is to create a huge log detailing things. With WebAPI configuration settings, the debug build can have huge amounts of logging, and the release version can easily turn all that off. Though it needs to be setup and the logging needs to be programmed. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
