Adding SOAP Web Services to .Net Core Projects
SOAP web services are not first class citizens in .Net Core. Not so long ago, Microsoft so eagerly spent a lot of resources to SOAP-based web services, "sold" it as HTTP+XML and even published a lot of libraries, software factories, guidelines and what have you for it. Now... oh, how times have changed!
The truth is, the campaign for SOAP web services was an industry-wide effort. The campaign was successful. Microsoft even has WCF to prove it. Many of the web services created are still live and functional today, and there are still new SOAP/WCF web services being created and published. SOAP and WCF are solid specifications after all.
In older versions of Visual Studio, it's quite easy to add web services as references to your project via dedicated wizard/dialogue. In Visual Studio 2017, this feature does not inherently exist for .Net Core projects. This does not mean though that you can't reference SOAP/WCF web services in your .Net Core projects. Microsoft provides a Visual Studio extension called Microsoft WCF Web Service Reference Provider to enable just that.
When installed, you can easily add SOAP/WCF web services to your .Net Core projects via wizard/dialogue. The WCF Connected Service extension actually creates a proxy class to represent the referenced web service. The current version is still in preview and you may still find yourself editing the generated code to add features like, for example, adding basic authentication support.
The good news is knowing that there is a way, and Microsoft recognizes the immediate need. There are many applications that consume web services. It would be a deal breaker if .Net Core would not support SOAP/WCF web services.
The truth is, the campaign for SOAP web services was an industry-wide effort. The campaign was successful. Microsoft even has WCF to prove it. Many of the web services created are still live and functional today, and there are still new SOAP/WCF web services being created and published. SOAP and WCF are solid specifications after all.
In older versions of Visual Studio, it's quite easy to add web services as references to your project via dedicated wizard/dialogue. In Visual Studio 2017, this feature does not inherently exist for .Net Core projects. This does not mean though that you can't reference SOAP/WCF web services in your .Net Core projects. Microsoft provides a Visual Studio extension called Microsoft WCF Web Service Reference Provider to enable just that.
When installed, you can easily add SOAP/WCF web services to your .Net Core projects via wizard/dialogue. The WCF Connected Service extension actually creates a proxy class to represent the referenced web service. The current version is still in preview and you may still find yourself editing the generated code to add features like, for example, adding basic authentication support.
The good news is knowing that there is a way, and Microsoft recognizes the immediate need. There are many applications that consume web services. It would be a deal breaker if .Net Core would not support SOAP/WCF web services.
Comments
Dot Net Online Course Bangalore
Dot Net Training in Chennai | Dot Net Training in anna nagar | Dot Net Training in omr | Dot Net Training in porur | Dot Net Training in tambaram | Dot Net Training in velachery
Post a Comment