Geeks With Blogs


View Anthony Trudeau's profile on LinkedIn

Add to Technorati Favorites

Anthony Trudeau

It's my first post of the new year.  I was hoping to do better at posting this year, but it's just not happening yet.  It's been an eventful year so far, first my wife has given birth to our first child, second we're in the process of having a house built in Georgia, and third we're trying to sell our current home in Virginia.

I just recently finished a project involving allot of legacy VB script within a workflow application (VisiWatch) that I hope to sometime in the future roll into Windows Workflow Foundation or other services.  I get a little diversion involving .NET to create a configuration tool for our VisiWatch solution.  It has been months since I've been able to do anything appreciable in .NET.  (My next project will probably be in a scripted barcoding software that can only barely be called a programming language.)  The good news is that there is a plethora of projects on the horizon that will all be .NET -- first the old stuff has to be firmed up.

I was going to create the configuration tool I mentioned using the smart client software factory (SCSF) which uses the composite application block (CAB).  However, my boss wants the tool quicker than I can deliver it if I were to add the learning curve for SCSF.  But, this evening I took some time to get a feeling of the basic project infrastructure created from the Smart Client project type and see what it would take to get it to work with the Infragistics NetAdvantage control set.

I initially suspected that the implementation would be quite involved.  But, it turned out that only a few simple if not monotonous steps are required.  The first step is to either build or add the Infragistics CAB project to your project.  The library in question is Infragistics.Practices.CompositeUI.WinForms.dll.  After the project is built or added you need to add a reference to it in the Shell and Infrastructure.Library projects.

Only the SmartClientApplication class needs to be changed in order to get your project to build successfully.  The first step is to add a using statement (Imports for VB) that references Infragistics.Practices.CompositeUI.WinForms.  The second is to change the class so that it inherits from IGFormShellApplication instead of the standard FormShellApplication.

At this point your project will build.  But, you'll have a bit to do in order to use the controls.  The first will be to create your own ShellLayoutView and ShellLayoutPresenter in the Infrastructure.Layout project which you will reference in the Module class instead.  Afer that you will need to register your UI extension sites as applicable (you can use the default classes and the Infragistics examples as guides).

Here is a summary of what you need to do:

  1. Add a reference to Infragistics.Practices.CompositeUI.WinForms to the following projects:
    • Shell
    • Infrastructure.Library
  2. Change the SmartClientApplication class as follows:
    • Add a using statement for Infragistics.Practices.CompositeUI.WinForms
    • Inherit from IGFormShellApplication
  3. Create a new pair or edit the ShellLayoutView and ShellLayoutViewPresenter classes in the Infrastructure.Layout project
    • Register the UI extension sites as needed
    • Refer to Infragistics documentation for examples of specific workspace setup
Posted on Tuesday, February 6, 2007 6:45 PM Infragistics , .NET | Back to top

Comments on this post: CAB and Infragistics

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Anthony Trudeau | Powered by: