Last post May 14, 2009 03:59 PM by atconway
May 08, 2009 10:30 AM|2ujohn|LINK
i need to develop a websevice in dot net 3.5 using c#, which should use WSE 3.0 for MTOM functionality.but i am unable to WSE 3.0 tool available inside dot net 3.5. i know that we can use WCF service to get mtom working . but the client doesnt want to use
wcf for time being.
is there any round way about getting WSE 3.0 working for dot net 3.5 ?
pls help me out in this.
thanks and regards,
May 10, 2009 03:31 PM|LiveTecs|LINK
Microsoft is no more going to support WSE 3 any more. All are now available in WCF.
May 14, 2009 03:59 PM|atconway|LINK
There is a way and I have had to do that myself, because I have not had time to convert my web service over to a WCF service quite yet.
The important thing to know is that all that tool did in VS.NET 2005 that was integrated into the project menu, was run the wsewsdl3.exe tool to generate the proxy classes for your project, and make some web.config configurations as well. All I do now is
generate the classes using wither a dummy project from VS.NET 2005 or the WSEwsdl.exe command tool to generate the proxy classes, and then copy them into my VS.NET 2008 project. It is a
really simple process and only takes about an extra 2 minutes and 1 extra step.
The best site to descibe doing this is below:
...or the MSDN site:
There is also supposably a way to create an Add-In for VS.NET 2008 that will emulate the steps done above and generate the additional WSE classes in the web service generated proxy code (Reference.vb or Reference.cs file). I followed all of the steps to
a 'T' and could not get it to work. I even added some comments on the Blog, but received no response. If you want to give it a try check out the following site:
However, I really think either using the command tool to generate the proxy into a dummy project and then copying into your VS.NET 2008 project OR keeping a VS.NET 2005 dummy project alive so you can generate the WSE proxy from there and then copy it into
your VS.NET 2008 project is easiest. Just remember to regenrate the WSE proxy using this process again if you need to refresh your web reference. Refreshing the web reference from VS.NET 2008
after copying over the WSE classes will overwrite them.
I believe Microsoft phased out WSE to ween developers to the path of using WCF, as WCF has all of the functionality of WSE 3.0 and more.