I’m a little late in announcing this. WSCF.blue is now formally released to web as v1. Although its only been out 3-4 days now we’ve crossed over a 100 downloads already. Whew. Looks like a lot of folk were waiting for this release 
Christian Weyer has blogged about the release. I would also like to call out Alex for taking so much initiative and coding till 3am on some days (and emailing the group at that time too !!). We definitely owe this release to him.
Now on to v2. My next post will be about the roadmap and our shopping list of features for the next few releases. Check out the final v1 release. Hope you like it. As always, your feedback and suggestions would be most welcome and appreciated.
WSCF.blue now has a new feature called “Paste-As-Schema” (which takes inspiration from the REST starter kit’s Paste-As-Type). Alex explains the new feature in detail in his post.
The MSI has now been updated to version 1.0.4. It is still formally in Beta-2. It also includes a few bug fixes in the original Beta-2 (1.0.3) release. Please check the CodePlex workspace for details. Hope you find the new feature useful. If you run into any issues do let us know.
Beta-2 of WSCF.blue is now available.
The big feature of this new beta is the standalone Data Contract Generation and we have also put in some other fixes and addressed some outstanding issues (as well as rolling up fixes since the last beta).
The feature list is as follows. The “More Information” links point to posts on Alex’s blog with screenshots and lots of details.
- The Generate Data Contract Code feature is now available and supports the selection of multiple XSD/WSDL source files. (More Information)
- When the Enable WSDL Endpoint option is chosen a reference to the Thinktecture.ServiceModel.Extensions.Metadata.dll assembly is automatically added.
- Support for VB.NET has been added to the code generation.
- You can choose if operation methods on the service class will throw a NotImplementedException, call an implementation method in a partial class, or will be defined as abstract methods. (More Information)
- Force the SOAP actions (Action and ReplyAction) applied to each operation contract follow the standard WCF format: <namespace>/<service>/<operation>[Response]
Hope you find this release useful. As always , keep the feedback and suggestions rolling in. Enjoy
So there’s been a few things happening on the WSCF.blue front. We’ve had some excellent feedback and also some feature suggestions, so all that has been rolled up into the install package. It’s still Beta-1, but the MSI has been updated to v1.0.2.
The main changes are
(1) the option to format the soapActions when setting the Action and ReplyAction so that it conforms to W3C standards. We had some issues with certain WSDLs where we were getting the replyAction set to “*” (and even svcutil was doing that) which affected the communication.
(2) Options to control the way the service class is implemented. Hitherto we have had the default behavior of the method throwing a “NotImplementedException” (which is a normal thing for a code-generator). But this can be limiting sometimes. So we now have options to either define the class as abstract or partial. Alex explains all this in his post.
Hope you find the new features useful.
