The WSE team recently ran a series of test passes with WSE 2.0 on .NET Framework 2.0 Beta 1 (aka Whidbey or VS 2005). We tried both the shipping version of WSE 2.0 and a recompiled version, but experienced a number of problems with both.
We know for sure that the soap.tcp transport is completely broken - incoming connections generally fail with a SocketException during Accept processing. We've also run into a number of problems associated with ASMX classes.
We're working with the relevant parties on the Framework team to try to resolve these issues, we believe that most of them are caused by changes made to the Framework itself, not by problems in the WSE codebase. Of course, .NET Framework 2.0 is still beta software and this is therefore to be expected despite all the effort that goes into trying to ensure backward compatibility early in the development cycle.
Current product plans are that WSE 2.0 will be supported on .NET Framework 2.0 when the Framework releases. Until then, we can't make any guarantees on whether the products will work together.
Sorry folks :-(
Posted by herveyw at August 24, 2004 09:58 PMPlease, during your testing, make sure that WSE is suitable (especially from a code-security standpoint) as a client protocol for a ClickOnce deployed app. I would like to use WSE for secure communications in a ClickOnce app, but I don't want to endure extra security challenges to accomplish this.
Also, generate Properties on the client proxy to enable data binding!
Thanks!
Posted by: Rob Cannon at August 25, 2004 06:51 AMI've been using WSE 2.0 on .NET 2.0 Beta 1 for several months and it has worked quite well. I am using it over HTTP so I haven't run into the TCP/IP problem you described. I'm glad the DataSet serialization issue has been fixed with SP1, but I still don't understand why passing a SoapEnvelope to a method on a SoapService results in a SoapEnvelope within a SoapEnvelope. You'd think the service would be smart enough to realize that it had received an envelope and not wrap the incoming Xml. This may be one of the issues you're talking about but other than that my experience has been positive. The only other thing I was disapointed not to see in WSE is that the WSDL generation API is private, similar to the vanilla Framework implementation. This would be a highly useful feature for those of us using web services "outside the box" and was my primary motivator to use a SoapService over a SoapReceiver.
Posted by: James Bong at September 8, 2004 04:39 PM