Note: this entry has moved.
The cornerstone of any highly extensible and pluggable framework is configuration. This is even more important in SOA architectures like Shadowfax (Sfx), because business actions (BA), service interface and implementation, pipelines, etc., must be configured. Configuring BAs is specially critical since a typical enterprise application will contain hundreds of them. A set of wizards for Sfx were released for that purpose.
First, what you'll see: after installing both MSIs in the distro, you'll have new items in the Add New Project and Add New Item dialogs, as well as some additional context menus.
All wizards can generate either VB.NET or C# code. Note that both language categories exist inside a new folder at the left called Microsoft IPE Wizard Framework. That's the framework these wizards are built on top, which I'll discuss in another post.
The Word document bundled with the distribution shows all wizards and the actions they perform. You have worked with wizards in the past, so I'll save you the hassle of reading how to use these ones. There's, however, a very interesting feature: you can modify the generated code for the classes, thanks to a template transformation engine (code-named T3 - Templated Text Transformantions) that is distributed with the wizard framework.
Under the wizard framework installation folder, by default
Files\Microsoft Application Blocks For .Net\Microsoft IPE Wizard Framework,
you'll find a
Templates folder, containing
Transformations subfolders. The last is
the one containing templates used for code generation. The templates are named
after the assembly using them (for Sfx wizards it's the
) plus the concrete wizard resource name. For example, the one used to generate
the BA class definition in C# for context invocation is:
If you have used CodeSmith, you'll
find the template syntax inmediately familiar, which is also similar to ASP.NET
one. Everything between
#/> (just like
%> counterparts) is considered
code that must be executed at template-rendering time. The language for this
code is specified through the
<#@ Template Language= "C#|VB" #/>
template directive. Everything else, is just text that is emited as-is. Here's
the BA class creation template:
Parameters received by the template at run-time, depending on user input, are retrieved at the beginning of the template through a service exposed by the container. You can add your own methods or change the base class of all generated BAs simply by modifying this template.
Wizards are deeply integrated with the IDE and the Sfx configuration file.
Therefore, in order to run the wizards you must specify where's the
configuration file. You do so by right-clicking the
file in the
Solution Items folder, and selecting
Wizards will show relevant information from both the current solution as well
as the configuration file when necessary. For example, in the screenshot above
you see a
Configure pipeline menu option. If you select it, you'll
enter a wizard that allows you to modify existing pipelines in the file. (I
have to show this because I like how it looks)
On the next step, you'll have the option of editing either a service interface or implementation pipeline. The dropdown below shows the actual pipeline names in the configuration file for the joinpoint you chose!
And in the next step, you get the current configuration, including handlers associated with the pipeline. You can add/remove handlers too, from a list that is also pulled from the config file:
This can be a real time-saver, and avoids occasional typos.
Currently, the following wizards are supported:
- Add Business Action: creates a new BA and optionally adds a new project for it.
- Expose Business Action as new Service Action: allows you to develop BAs and later configure and expose them as service actions in Sfx.
- Configure Pipeline: the one you saw above.
- Add New Service: this is probably the first one you should run. It goes through all the steps to setup all projects that will be needed for developing for Sfx. This includes creating a folder for the service you're creating (i.e. Accounting), creating or selecting the project that will hold message definitions, and the one for BAs, creating a new BA (this is basically the same as the first wizard, embedded in this one), configuring it with Sfx, exposing it through a WebService interface (creates the WebService class as well), and updating deploy scripts.
- Add Custom Handler: creates skeleton implementations of the three types of handlers, Atomic, Stateful around and Stateless around.
- Create Service Gateway Class: creates either a MSMQ or Remoting client proxy class. Specially for MSMQ, this is a huge plus!
What other wizards would you like to have?
In a future post, I'll discuss the architecture and integration features of the Wizard Framework that backs all these wizards, which are 100% .NET code (no HTML or JS!), are defined in XML and customized through well known TypeConverter and UITypeEditor classes.