Archive for the ‘WSCF’ Category
Its the first time a trans-atlantic webcast has been attempted and that too with video chat and desktop sharing via OCS so there are slight lags in the audio sync to the face to face bits. However, the video is primarily an on-screen demo so audio sync doesnt appear to be much of an issue.
Check it out and post your feedback on the episode and the tool.
I had previously written about the WSCF Roadmap. These have now been entered into the IssueTracker on the workspace. WSCF vNext is underway but we need to know what features to invest in. What additions to the toolset would help your productivity and delivery.
The main items are listed below. Which of these would ‘rock your world’ and which of these do you not give 2 figs about? Have a look and then head over to the workspace and get voting.
- T4 Templates
- DataContractSerializer support
- Contract First Workflow Services
- Re-platform with FeatureBuilder
- Merge ‘Classic’ and ‘Blue’
- Externalized API
- Persistence & Reload of settings
- New command line
- Other bindings
- Multiple SVC files
- Custom Behaviors
- Incremental code-gen
- WS-Addressing Support
- Flexible Naming conventions
- Integration with ServiceFactory
- New/additional UI
If there are other items that we could consider, let us know on the forums or add items to the IssueTracker. Looking forward to hearing from you.
- How to model your data
- How to model your messages
- How to model your interface (build a WSDL from a set of XSD files)
- How to use advanced options such as Fault Contracts as part of your interface
- How to generate a service side stub from the WSDL
- How to generate client ‘proxies’ from a WSDL
- How to work with the auto-generated code and fill out your implementation
- How to generate data contracts from a WSDL
The walkthrough applies to both VS2008 and VS2010 as the steps are the same. The only difference is the config files for WCF4 and if you run into any problems in this area please let us know and we can update the content.
We hope you find this to be useful.
WSCFblue v1 has been a really successful project and we’ve had some great discussions on the forums, feature requests (most of which we have been able to provide) and so on. For a long time the team has been thinking about the next generation of WSCF tooling, taking what we have now to the next level and we have put together a list of things for which we would love to get your feedback and ideas to help prioritise.
So here’s our laundry list. You can provide feedback here or on the CodePlex workspace where I shall put them up as work items so you can vote on them if you like.
- T4 templates : We’ve had numerous requests for additional settings to allow users to ‘tweak’ the generated code ‘ever so slightly!’. To an extent, this can be done quickly as we implement ‘decorators’ to allow us to change the code depending on the options, but for many folk the ‘Rolls Royce’ of customising the code generation would be to control it through T4 templates. Having said this. there are (big) issues to consider. The first thing is that the onus is on the end user to not mess with the templates because T4 (as well as other code gen tools) will provide a long rope on which we could easily hang ourselves . The second issue is that if we upgrade the templates, then again the end user will have to migrate any customisations. So in some ways T4 could be a double edged sword.
- Merge ‘Classic’ and ‘Blue’ : The ‘Classic’ / ASMX code generator is still available on a separate CodePlex project. While we havent made any formal MSI releases, there have been a number of contributions to the source especially to the command line options etc. While WCF is the preferred web services implementation framework, IMO, ASMX will be around for a long time and it would be useful to support that. It would be too much work for us to maintain two separate code-bases so perhaps it’s time to bring Classic into the Blue workspace.
- API : While WSCF is primarily an add-in at the moment, it would be useful to externalize the API of the engine. The framework currently covers major services such as WSDL Generation, WSDL Import/Parsing, Service side stub generation, data contract gen and client side proxy gen and configuration management. A proper API would make it usable by other tools (such as my own MockingBird – which could ‘outsource’ the metadata import of multi-part WSDLs to WSCF) as well as other tools that developers may write.
- Persistence + Reload of settings (all dialogs and WSDL wizard ) : For some of the code gen dialogs we allow the user to save the settings. However, this file is in the users profile temp folders. Storing these settings along with the code as well as allowing the code-gen dialogs (and the WSDL Wizard) to load a pre-existing config file would be very useful in scenarios where we only need to change one setting but dont want to go through the entire series of steps in the wizard.
- New command line (can use “settings” files) : The command line interface is in need of an overhaul. We could allow the user to use the ‘settings’ files mentioned above as part of the command line. The new command line would also target both Classic and Blue if possible.
- Support other bindings : We only use BasicHttpBinding now. So far no one has asked for anything else. Should we consider adding an option to the dialogs that allow you to pick the binding (perhaps including custom bindings, say, via MEF?)
- Customized mapping of endpoints to SVC files? (multiple svc files) : We currently support only one endpoint (SVC file which points to the generated interface) out of the box. Business services usually have different endpoints (possibly with different bindings) to support things like customer access, management/ops access and so on. Is this something you would want ? Currently you can do this by creating another WSDL (importing the same schemas if needed) and driving the code gen from there, but since the metadata/WSDL for a service is always the same no matter how many endpoints, perhaps there needs to be an option for going from one WSDL to multiple SVC files ?
- Incremental code-gen (ie: what if we want to add extra operations to an SVC file or WSDL) : This is in early stages of thinking. Should the tooling allow you to add extra ops or would it be better to run the wizards again ? If we persist/re-load all wizard settings, then this wont be an arduous process anymore. I’m leaning towards the latter option because I would rather not tinker with code that could have been customized.
- Additional behaviors : Christian Weyer wrote a custom “FlatWSDL” behavior that allows the service to expose a single consolidated flattened WSDL. Perhaps this can be provided as one of the options for the service. Again, (via MEF) we could pick up any number of custom behaviors and allow the user to select them.
- WS-Addressing support in WSDL wizard : The title says it all.
- More flexible naming conventions : What would you like to see here? would T4 supersede this?
- Contract First Workflow Services (.NET 4) : There is no support in WF4 for proper contract first development for various reasons. IMO, its more of a lack of time to provide the tooling and we may see something in service packs or upcoming versions if enough folks shout loud enough and/or if there are commercial justifications for the same. Anyway,rationale aside, is this something you would like to see in WSCF? Now do keep in mind that we havent worked through this issue in detail and it maybe that the lack of support goes beyond tooling so being able to code-gen the XAML will not provide any guaranteees it will actually work, be rendered correctly by the designer and so on. But i think its worth considering and if you are a WF expert and have done anything in this area , we’d love to hear from you and maybe work with you on the same.
- Integration with Service Factory : Would it be useful / make sense to link this with the Service Factory Modeling Edition (in its VS2010 or beyond incarnation). What are the touchpoints you see?
- Feature Builder : Now that Feature Builder has emerged as the primary vehicle for providing automated guidance, we’ve been thinking that WSCF should leverage Feature Builder. One of the reasons is that as we expand our functionality , wizards and single screen code gen dialogs are just too linear and do not provide enough guidance on what options or sets of options should be chosen for your scenario.
- WPF UI : We’ve (at least Alex has) been playing around with MVVM a little to see if we can rewrite the WSDL Wizard which is currently tightly coupled to the code gen engine. Given that we have opted for a full on refactoring (explained below), this may not be necessary, but on the other hand if we are going to support lots more options etc then the UI’s are going to need an overhaul. Let us know what you think of this idea.
That’s our list as it stands now. We are continuing to provide point releases of V1 but for many (if not all) the features listed above, a full on refactoring of our code base is essential, which is already underway (For example, if we merged Classic and Blue, I would expect to be able to use the same core engine of ‘Blue’ , which evolved significantly from the ASMX days, and just ‘plugin’ the ASMX generation, but with the current code structure this is not possible). So it’s quite likely that most of the features above will be v2.x.
Please do provide your comments and feedback on the roadmap and help us to prioritise. We want to continue to make WSCF blue the premier web services development toolset for the .NET community. Looking forward to your feedback.
WSCF.blue v1.0.7 now supports VS10 RC in addition to VS2008. There are no new features as such although v1.0.6 which we released a short while ago fixes a number of important bugs in data contract generation. Alex , our code-master extraordinaire, blogged about the 1.0.6 release here .
The generated code has not changed (from previous versions) and runs fine in VS10. With WCF 4′s configuration enhancements, it is even easier to merge config from the output.config file which we generate to the web.config or app.config. Simply copy the bindings and service elements across. Check the release notes for some info on how to handle the <serviceHostingEnvironment multipleSiteBindingsEnabled attribute in WCF 4.
Grab the latest release and let us know what you think. Please note that VS10 Beta-2 is NOT supported because of a number of bugs in the context menus and command bar area of VSX. Alex has already started work on V2 which will be a bigger release and I will write about our main themes and roadmap shortly. We are looking forward to your feedback (now and on the roadmap) to help plan features and releases. Hope you find our latest release useful.
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.
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