Untitled

Random thoughts about everything and nothing

Archive for the ‘how to’ Category

How to: Adding coordination to your GAT action execution

with 2 comments

At some point during GAT action execution, one might need some sort of conditional processing. 

For instance, depending on some choices made during the gathering wizard, some actions won’t be executed.

In the example I’ll be using, the user is prompted to fill in two messages.  Next to these, two checkboxes will indicate if the corresponding message will be displayed (not much of a show-stopper there…;-)).

Read the rest of this entry »

Advertisements

Written by Michael

November 21, 2007 at 1:26 am

Registering your GAT package in the Experimental hive

with 8 comments

During the Web Service Factory Workshop last week we saw a new feature in the GAT / GAX July 2007 release…registering your GAT package in the Experimental hive.

To accomplish this you simply need to add the <RegistrationSettings> element to your guidance configuration file:

<GuidancePackage xmlns=”http://schemas.microsoft.com/pag/gax-core”
    Name=”ExperimentalPackage”
    Caption=”ExperimentalPackage”
    Description=”Package to demonstrate the experimental hive installation”
    BindingRecipe=”BindingRecipe”
    Guid=”88795b6a-6624-448a-8f07-5fea64548753″
    SchemaVersion=”1.0″>
<HostData>
    <RegistrationSettings>/Hive=8.0Exp</RegistrationSettings>
</HostData>

That’s it.  Next time your perform a ‘Register Guidance Package’ action, the package will be registered into the hive.

Notice: 

  1. It think this even works with the Clarius SFT, which overrides the ‘Regular’ or ‘Regular & Hive’ options.
  2. For those of us debugging the GAT packages using the ‘Debug | Start external program’ feature (as explained by Tom Hollander here), simply add the ‘/rootSuffix Exp’ value in the ‘Start Options | Command line arguments’ box.

Written by Michael

November 20, 2007 at 9:14 pm

How to: Manually update references in your Visual Studio projects

with 5 comments

It’s probably me…

but when I replace an existing reference (and i mean a none project reference), the new version isn’t (always) used at runtime.  Visual Studio 2005 displays the correct version number in the property pane, but the older version keeps popping up.

Read the rest of this entry »

Written by Michael

August 1, 2007 at 1:24 pm

Posted in .NET, how to, Visual Studio, VSTS