Cabana Installation and Release Notes

Welcome to the Cabana Source Code!

These notes are divided into two sections:

Cabana requires DevForce

The Cabana application will neither com= pile nor run without DevForce installed. Fortunately, DevForce is easy to get.

You can download and install a DevForce edition such as DevForce Express from our website for free at www.ideablade.com/downloads.html.

Installation of Cabana is nearly painless but there ar= e a few places that can give you momentary trouble. For example, you may need to tweak the connection string to find your copy of the IdeaBlade Tutorial database.

Please read the In= stallation Notes carefully !

Please read also the document “CabanaStructure” that descr= ibes the files and solution structures. You can get the latest version from our website at = http://www.ideablade.com/Cabana/CabanaStructure.pdf

Both documents are absolute “musts”.

What Cabana Is and Is Not

Cabana is supposed to be … well, fun. It’s intended to show you some of the things you can do as a DevForce enterprise application developer.

Cabana is not intended to be a sophisticated application

Cabana demonstrates intermediate and advanced techniqu= es in the context of a Composite UI Application Block (CAB) application. We want = the application itself to be as simple as possible without obscuring the key points. Our customers build large, sophisticated applications that draw on these techniques.

Cabana source code is not for beginning DevForce application developers=

Cabana is a challenging place to start if you have just installed DevForce. Please try the DevForce tutorials first as they establi= sh a foundation for the ideas and suggestions here. Please feel free to explore = Cabana for interesting details and for clues about solutions to advanced issues – just keep in mind that it is a tutorial, not a real application.

Install Cabana Code (for DF v.3.5.3.1)

Installation Basics

Cabana installation changes in version 2.3.0.0.

The basic instructions have been moved from this docum= ent to the “Getting Started Guide”, available in the download package = and from the Cabana website (www.id= eablade.com/Cabana).

Pick the Right Download File

There are two versions at this time.

CabanaDotNetCS.zip

Dedicated to applications based on the DotNet UI controls only. DevForce Express users should use this package.

CabanaDevExCS.zip

Dedicated to applications based on the Developer E= xpress UI controls.

The Cabana in this package is rooted in the Develo= per Express UI controls but includes a mix of DotNet and DevEx views.

You must have DevForce Professional or DevForce Enterprise editions to use this package.

Unzip download package into the directory of your ch= oice.

Open the “Getting Started Guide” and take = it from there.

CAB Source

You don’t need the CAB or SCSF source code to use Cabana. You don’t need the Guidance Automation Toolkit or Guidance Automation Package either because Cabana doesn’t use SCSF recipes[1].

It is often useful to see how CAB code actually works.= You won’t be able to debug into CAB or SCSF (sad to say) but you can open= up the solutions and read the code.

Get them from http://www.codeplex.com/smartclient.

Troubleshooting the Install

The “Getting Started Guide” has troubleshooting suggestions. The ones that follow here may also be of value= .

Here we cover a few common “gotchas”

1.&n= bsp; DevForce version incompatibility

2. = Solution seems not to build or run

3. = Visual Studio complains during build (phantom messa= ges)

4. = Can’t find IdeaBladeTutorial database / wrong IdeaBladeTutorial database

5. = Can’t get the Visual Studio Toolbox to work properly

6. = Test projects don’t compile or run; missing NUnit.

DevForce Version Compatibility

Your version of DevForce (DF) may not be the same as t= he version we used to build Cabana (currently 3.5.3.1). If your DF version differs from the Cabana version, you may be ok. If Cabana won’t build, you may only to fire up the Object Mapper and regenerate the DataRow classes.

If you are using a different version of DevForce (not recommended), you may need to run the Object Mapper and regenerate entities in the business object project, Cabana.Model before y= ou build Cabanaxxx.

However, we strongly recommend that you use the latest version of DevForce and Cabana.

Solution Seems Not To Build or Run

There are two solutions: CabanaLib= and Cabana= xxx.

You must build CabanaLib first in order to build = the projects needed by the application. These projects output their assemblies = to the “Lib” directory. If you neglect to build it and build the other solution, you’ll get a bo= at load of errors such as:

You may be tempted to run CabanaLib= after you’ve built it. It does not run.

There is only one solution that runs: Cabanaxxx (as in CabanaDotNetCS.sln).

You must proceed in the following order:

ð Build CabanaLib first.

ð Build Cabanaxxx second.

ð The startup project is called CabanaShell; this should start when you press F5

Projects in the ExternalSource folder are unavailable

There is an “ExternalSource” folder in the application solution. All of its projects are unloaded and, thus, “unavailable.” That’s how it is supposed to be; the file “ExternalSourc= e.ReadMe.txt” in the folder explains why.

Visual Studio complains during build (phantom messages)

There is some misbehavior when you build either Cabana= solution that we haven’t learned how to cure.

The behavior is alarming but harmless; VS is complaini= ng about nothing.

You can be assured of this by the fact that the build succeeds despite the noise.

“Missing components” Warnings

You may see a flurry of warning messages after the bui= ld.

Of greatest apparent concern are warnings that read as follows:

Warning The referenced component 'Scsf.Infrastructure.Interface' could not be found=

This is an illusion, an artifact of the build process.= In fact, all components were found.

Can’t Find IdeaBladeTutorial Database
Cabana gets its data from the IdeaBladeTutorial databa= se that ships with DevForce – the one we use for our DevForce tutorials.=

You will need the latest version of this database. You should confirm that you have the correct IdeaBladeTutorial database install= ed and that the connection string(s) shipped with Cabana actually work in your= SQL Server.

Use the Appropriate Tutorial Database

The latest Cabana depends upon the IdeaBladeTutorial database that shipped with DevForce version 3.5.2.2. If you installed this version – or a later version – you are in good shape …

… unless you neglected to replace a previous ver= sion of the database.

When DevForce installs, it checks to see if you have a= lready have an IdeaBladeTutorial database in your SQL Server. You won’t if y= ou are a first time DevForce installer. You will have one if you’ve installed DevForce before.

The DevForce install does not remove a pre-existing IdeaBladeTutorial database.

This is intentional. You may have made changes that = you want to keep.

But this could mean that you have a tutorial database = that is missing tables or data that Cabana requires. Such is certainly the case = if your tutorial database came from a DevForce version prior to 3.5.2.2.

You can contact support to get a copy of the IdeaBladeTutorial database.

You will have to do the following:

ð Launch SQL Server Manager

ð Detach IdeaBladeTutorial

ð Locate the database files[2] and squirrel them away (optional).

ð Run the tutorial database installer from “Start | IdeaBlade DevForce | Tools | Database Installer”.

ð Confirm that the database was installed[3].

Connection String

There are connection string specifications in several places, all of them reading as follows:

Provider=3DSQLOLEDB.1;Integrated Security=3DSSPI;
Persist Security Info=3DFalse;Initial Catalog=3DIdeaBladeTutorial;

Data Source=3Dlocalhost

You won’t be able to connect (and login) if any aspect of this string is wrong, such as:

· You’re not using MS SQL Server (2000 or 2005)

· You have a named instance of MS SQL Server (rather than a default instance)

· You can’t use the SQL OLEDB provider

· You can’t use integrated security (Win= dows Authentication)

· The database isn’t named “IdeaBladeTutorial”

· You can’t refer to the database server= as “localhost” (e.g., named pipes not enabled for your server).

Launch the Object Mapper while examining the Model pro= ject to discover if this is a problem for you. If the Object Mapper can’t = find the database, you’ll have to find the connection string that does. The DevForce Installation Guide and Developer Guide offer some useful discovery tips.

Once you have a working connection string, you’l= l have to put that string in the following places:

· The Object Mapping file for the Model project (via the Object Mapper)

· The Object Mapping file for the Server proje= ct (via the Object Mapper)

· The two RdbKeys in the AppHelper.IdeaBlade.ibconfig; remember to rebuild - not just build – = this project after you make these changes.

The solution incl= udes an application, DbConnectionCleaner, that will guide you through the process of setting up a working connection string.

ð Launch Visual Studio.

ð Open the “Setup F= older”

ð Select the “IdeaB= lade.DbConnectionCleaner” project

ð Right-click the mouse a= nd select “Debug | Start new instance” from the context menu.

When you decide to explore the n-tier deployment opt= ions, you’ll also have to correct the strings in:

The n-tier deployment of Cabana is not ready yet.

· The connection strings in the [DataSourceKeyInfo] table in IdeaBladeTutorial; see the next topic if you don’t have such= a table.

· The “security” RdbKey in the Server.IIS. IdeaBlade.ibconfig (but not in the “default” key).<= /p>

· The “security” RdbKey in the Server.WinSvc. IdeaBlade.ibconfig (but not in the “default” key= ).

You must make these changes manually. DbConnectionCleaner will not help you.

CAB Designer Components in Visual Studio Tool= box Fail

So you want to drag a CAB component from the toolbox o= nto the canvas?

You don’t have a Toolbox tab with CAB components= ? Skip the “problem” section below and go to the Remedy”.

Problem

You might encounter two problems.

· The Toolbox tab with your CAB components disappeared.

· Visual Studio throws a fit when you drag a component onto the canvas.

No Tab? The likely cause is that Visual Studio canR= 17;t find the directory where it thinks these components should reside. This has= to be the Cabana “Lib” directory. Chances are you erased your Caba= na solution or moved it. Go to the remedy section.

You have the tab but you get this:

The likely cause here is that your toolbox tab points = to CAB components from assemblies that are different from the ones you are referen= cing in your application solution.

Maybe you have other CAB applications and your Visual = Studio tab components reference the dlls in that solution?

In this example, my UserControl is in a project that r= eferences the Microsoft.Practices.CompositeUI. Winforms assembly in the application’s “Lib” directory but the Visual Studio toolbox component references the Micros= oft.Practices.CompositeUI.Winforms produced by building the CAB source code[4].

What a pain!

Remedy

You must create a toolbox tab with CAB designer compon= ents from the same assembly that your project is referencing. That means the too= lbox tab must reference the assemblies in the Lib directory of your application.=

Do the following:

ð Add a new tab to the toolbox, e.g. CabanaLib=

ð Right-click in the tab and pick “Choose items … ”

ð Click the Browse button and navigate to the = Lib directory

ð Pick the Microsoft.Practices.CompositeUI.Winforms assembly

ð In the filter text box, type “Microsoft.Practices.Comp”

ð Click OK

ð Click the Browse button again

ð Pick the DotNet.CompositeUI.Extensions assembly

ð In the filter text box, type “Composit= eUIE”

ð Click OK

You are done unless you are using third party contro= ls. If using third party controls such as DevEx, continue

ð Click the Browse button again

ð Pick the DevEx.CompositeUI.Extensions assembly

ð In the filter text box, type “Composit= eUIE”

ð Click OK

Test Projects don’t build or run; missi= ng NUnit

Unit testing of Cabana is not ready yet= .

The test projects (all ending in ".Test") re= ly upon NUnit, the popular and free unit testing tool.

This installation package sets the solution build configuration to exclude these projects. Many of you will not have NUnit installed and these projects did not build successfully for want of the NUn= it libraries.

This means you can’t test properly until you add NUnit and include the test projects back into the build ̵= 1; a practice we strongly recommend.

You should use unit testing in your application and = Cabana offers clues as to how to proceed. Here’s how to re-engage unit testi= ng with Cabana.

ð Shut down Visual Studio.

ð Download NUnit v.2.4.1= for .NET 2.0 and install it.

ð Launch Visual Studio.

ð Open the “Configuration Manager” from the tool strip.

ð Find the test projects and check their checkboxes so that they are included in future builds.

ð Rebuild the solution.

Install IdeaBlade CAB Wizards & Templates

Many of you have = heard of the Smart Client Software Factory (SCSF) and its ability to automatically generate applications, projects, view/presenter pairs and other useful code= .

It does so by means of the Guidance Automation Toolkit= (GAT) and “recipes” that ship with SCSF.

Most of the shipped recipes are really just tutorial examples. We wouldn’t use them for production code.

The Patterns and Practices folks understand this full = well and encourage us to develop our own recipes to suit our particular applicat= ion development needs.

Unfortunately, recipe development is difficult (to say= the least). We have gone in a different direction to achieve the same effect. We are promoting the use of Visual Studio Templates, supported by wizards.

These are describe in their own “Getting Started Guide”, available in the download package and on the web.

You can learn about Visual Studio 2005 Templates at http://msdn2.microsoft.com/en-us/library/6db0hwky.aspx.

Visual Studio Templates in Cabana versions pr= ior to v.2.3.0.0

Earlier version of Cabana introduced bare bones Visual Studio templates for rapidly developing views. These have been supplanted by the “Wizards & Templates” feature introduced in v.2.3.0.0.<= /p>

The Cabana Project team has not yet tackled the intric= acies of GAT recipe development. In the meanwhile, we have converted some code fi= le collections into Visual Studio Templates.

The default VS template capabilities are not nearly as= rich as GAT’s so we cannot come close to duplicating the SCSF / GAT experience. But we do have some templates that can speed your development t= ime and, in this section, we show you how to install them.

Release Information

Version 2.3.0.0

This release is built for DevForce vers= ion 3.5.3.x. It will not compile for earlier versions because of an important change to the IdeaBlade.Persistence.Entity class affecting the implementation of IDataErrorInfo.

This is a major release that introduces Cabana Wizards= .

There has been some refactoring but the most significa= nt changes have been to the names and locations of many classes and assemblies – changes in support of the Wizards.

Cabana installation changes profoundly. The new “Getting Started Guide” explains installation anew and also cov= ers how to use the Wizards to build your own Cabana-style application.

Change Details

Forthcoming. Please check the website for the most rec= ent Release Notes (www.ideablade.co= m/Cabana).

Version 2.2.0.0

This release is built for DevForce vers= ion 3.5.2.x. It will compile and run on DF 3.5.1.1 but you must have and install the updated IdeaBladeTutorial database distributed with DF 3.5.2.3.

This is a major release with new patterns and a massive refactoring. It is, in effect, a code reset.

Please read the document “CabanaStructure” that descr= ibes the files and solution structures.

This document is an absolute must. You can get the lat= est version from our website at http://www.ide= ablade.com/Cabana/CabanaStructure.pdf.

Documentation remains rough. Improving on it is our hi= ghest development priority and you should see new material in the next month or t= wo.

“CabanaReference&#= 8221; is a draft of the architecture with numerous class diagrams: http://www.ide= ablade.com/Cabana/CabanaReference.pdf.

ObjectBuilder Version Nightmare

Previous Cabana versions relied upon the Microsoft.Practices.ObjectBuilder assembly produced from source code we all= can download. This was version 1.0.512= 05.0.

When they built Enterprise Library version 3.0 using ObjectBuilder, they decided that the ObjectBuilder assembly should be stron= gly named and signed with their certificate. They didn’t change the code = but they did produce a new build with version number 1.0.51206.0.

This creates a significant hardship for CAB application developers. Our application can only refer to one version of the ObjectBuil= der – either 1.0.51205.0 or = 1.0.51206.0.

If we want to use Enterprise Library v.3, we have to reference the 1.0.51206.0 ObjectBuilder. We can still look at the source code – it’s the = same as for 1.0.51205.0; but we can’t debug into it because we don’t have the pdb files and the specific source code files used to build 1.0.51206.0. Moreover, it is easy to have dangling references to 1.= 0.51205.0.

Separation of “our” code from “your” code

One of the most important developments, beginning in t= his release, is the separation of the “application” representing wh= at you might build from the source code that third parties – mostly us at IdeaBlade – will maintain.

This separation is evident in the delivery of two solu= tions, = CabanaLib and CabanaxxxCs.

The build implications of this separati= on are covered in the Installation guide above.

The goal is to make it easier for you to discard Cabana while leveraging the Cabana infrastructure. The distribution of classes bet= ween these two solutions is covered thoroughly in the CabanaStructure document.

DotNet and DevExpress Versions

Cabana, the application proper, now comes in two flavo= rs for the DotNet and Developer Express UI control suites: CabanaDotNetCS and CabanaDevExCS.

We are working on a version for Infragistics controls.

The DotNet ve= rsion uses nothing but DotNet controls.

The DevEx ver= sion uses a combination of DotNet and Developer Express controls. The DevEx Caba= na sports a different look and an extra "Admin" module that demonstr= ates a nested grid (aka, drill down grid).

We intend it to be 100% DevEx controls some day but, f= or now, we’ve at least shown the way.

The DevEx CAB wrappers date from 2006. There was a new version of these wrappers just before this release; we̵= 7;ll incorporate them in the next Cabana version.

The DevEx version requires at least the trial version = of the Developer Express WinForms control suite (that's what I use). You can get it from http://www.devexpress.com/.=

This CabanaDevEx version was built with DevEx suite 7.1. DevEx just moved on to 7.2. Unfortunately, you can’t= get the trial version of 7.1 from DevEx and neither Cabana or DevForce 3.2.2.2 = will work with 7.2 yet.

The third party control vendors are alw= ays doing this to us. We’ll catch up next release. Meanwhile, if you don’t have DevEx and you want to try Cabana, contact IdeaBlade support and ask them to send you a copy of the= DevEx 7.1 trial.

The Admin Module

While the Admin module is nominally concerned with maintaining user permissions, please be aware that it is just a demo and th= at this version of Cabana does not make use of the “security” tabl= es that are the target of the module nor can this version of Cabana modify tho= se tables.

The Admin module is also interesting for its use of “business object proxy” classes – classes that stand-in f= or persistable business objects. We’ll discuss the “why” and “how” of this technique in future documentation.

The DotNet version does not have the “Admin” module found in the DevEx version as the module’s primary purpose is to demonstrate drill-down grids … a feature not available in DotNet’s grid controls.

Templates

There are new view templates reflecting our ability to= get rid of superfluous class files in this release.

There are some very cool templates on the way for

· building a new application from scratch

· adding a module

· adding a page to a module

You should be able to punch out a new application in a= bout half an hour. We’re polishing those now and will release them very so= on.

Documentation

Documentation is the gravest weakness of CAB and of Ca= bana.

We’ve added some to this release such as the “CabanaReference” document, available at www.ideablade.= com/Cabana/CabanaReference.pdf, describes the architecture and has many class diagrams. It’s still a = work in progress.

We’re working on some “how to” scena= rios describing both the “how” and the “why” of common development tasks.

We expect to produce some videos in the next few month= s.

Miscellaneous

The source code is dotted with commented out alterna= tives. For example,

· You can turn off the stopwatch logging by us= ing the DummyStopwatchLogger service; see FoundationModule.FoundationServices.

· Change visibility of a tab in Infrastructure.Foundati= on.DemoDotNetTabVisibility in the Miscellaneous folder.

· It seems the easiest way to change a page controller’s EntityManager is by overriding GetDefaultEntityManager= as illustrated in Cabana.UI.SalesOrder. CustomerSearchPageController.

You’ll have to hunt for the others.

Version 1.0.4.0

This is the last Cabana release for DevForce version 3.2.1.x. The next releases will require DevForce version 3.3.0.x.

I heavily refactored the PageController for this release because I noticed that

· EmployeePageController and Custom= erPageController were very similar.

· Both were hard to follow.

· The tab building logic was similar across the tabs and across the pages.

These conditions cry out for refactoring ... and I h= eard the cry:

· An abstract base class for page controllers called EntitySummaryDetailPageController.

· Instances of it such as EmployeePageController<= /span> and CustomerPageController.

· TabViewBuilder, another abstract b= ase class that follows the Builder design pattern. Each TabViewBuilder instance creates and holds a TabPage view and presenter.

· TabViewBuilder subclasses implement the specifics of a TabPage for a particular purpose.

<= span style=3D'mso-list:Ignore'>o&nb= sp; The GeneralTabViewBuilder is used to b= uild a TabPage that provides more detail about the current entity in the main BindingSource. The “General” tab is a typical example.

<= span style=3D'mso-list:Ignore'>o&nb= sp; Tab-specific subclasses are defined as private nested classes of their parent Controller classes. Inside Employ= eePageController, for example, are OrderMasterDetailViewBuilder and EmployeeCustomersViewBu= ilder.

These are private because (a) no client of the Controller class needs to kn= ow about them, (b) they do not have any demonstrable re-usability elsewhere, a= nd (c) keeping them in the Controller class file makes them easier to examine = and understand. They could easily be pulled out and made internal = or public= if the need arose.

· TabViewBuilderList , a class which holds TabViewBuilder instances and facilitates calling one of the TabViewBuilder “build phase” methods across all to its contained instances.

This expedient cleaned up the Controller code considerably and made adding = a TabPag= e as simple as adding its TabViewBuilder to the Controller’s TabViewBuilderList.

I added the first two Visual Studio Item Templates i= n this release:

Item Template	Description
ControlView	A C# template produc= ing a View / Presenter pair in which the developer uses the ControlBindingManager= UI Designer to populate the SmartPart view with loose controls and bind t= hem to properties of objects in a BindingSource.
GridView	A C# template produc= ing a View / Presenter pair in which the developer uses the DotNetDataGridView UI Designer to add columns to a DotNet DataGridView and bind them= to properties of objects in a BindingSource.

The source for these templates is in the zip files in = the ItemTe= mplates directory in the root of the Cabana distribution zip.

Version 1.0.3.0

This is the first version to be deployed as an n-tier application from our website. There are only very minor changes.

SplashForm

I’ve added a SplashForm so that Cabana displays something to amuse the user while CAB builds the pages.

I found that this was especially important on “normal” machines accessing our app over the web. It takes an uncomfortably long time for CAB to do whatever it does. Maybe there is some latency on the IIS side too.

I threw this in as a total hack (see ShellApplication)= . I made no attempt to reach for resources in a decoupled way; I just jammed th= em into the form.

I also rudely abort the thread that displays the splas= h; this is crude and generally a no-no. But it’s only a splash page so I hope I’m forgiven.

Performance and Span Queries with GetManagedChildren()

I generalized the approach to span queries that was introduced in Version 1.0.2.0.

I added overloads to the DevForce GetManagedChildren method in the IdeaBlade.Cab.EntityModel.CommonEntity class so that = one can add spans (or otherwise tweak) the method with which DevForce implement= s a child relation property such as Employee.Orders.

See the revised GetEmployeeOrders method in Employ= eePageController for an example.

Version 1.0.2.0

This is the third public release. The visible changes = are small but Cabana has taken an important step forward: It is now deployable = as a ClickOnce application in both 2-tier and n-tier modes.

Performance and Span Queries

N-tier deployment revealed a common performance issue:= too many round-trips to the server when fetching data for grids. This was not apparent in development where all tiers are on the same box. It should up in 15-30 second delays in n-tier.

Spans are the usual remedy and they worked again here.= See the GetEmployeeOrders method in EmployeePageController for an example.

QueuedCall

I generalized the QueuedCall class in IdeaBl= ade.Cab.Library.Vutility so that it can represent any command that needs to be delayed during view configuration.

It’s current only use is to postpone the data bi= nding commands issued to presenters by their views. This is a necessity when the = view issues the command before the view’s BindingSource has been made ready. DevForce data binding handles this well but examples of raw .NET data binding don’t work unless the actual <= span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>BindingSource is known and prepared. If the presenter were to data bind when asked, it wo= uld fail.

I saw this as merely one among many possible cases in = which the view would ask the presenter to perform a function that it was not read= y to perform. Rather than blow up or do the wrong thing, the presenter can queue= the command and try it again later when the conditions are ripe.

QueuedCall takes a subroutine to call (the command), = its argument(s), and a test method that indicates if the requisite conditions f= or calling the command have been met. Both methods are delegates – typic= ally instance delegates – so they can have access to variables and methods= of the presenter instance in which they are defined.

SplashForm

I’ve added a SplashForm so that Cabana displays something to amuse the user while CAB builds the pages.

I threw this in as a total hack (see ShellApplication)= . I made no attempt to reach for resources in a decoupled way; I just jammed th= em into the form.

I also rudely abort the thread that displays the splas= h; this is crude and generally a no-no. But it’s only a splash page so I hope I’m forgiven.

Version 1.0.1.0

This is the second public release.

Infrastructure Project Re-organization

Infrastructure projects have been re-organized as part= of a project to

· improve the clarity of what they do

· completely separate (a) the source files provided by Smart = Client Software Factory (SCSF), (b) the IdeaBlade files, and (c) your files. The “your files” in this case is the Cabana sample application file= s.

The goal is that you could completely replace just the Cabana files with your own material and take advantage of the code “assets” provided by SCSF and IdeaBlade.

SCSF will change its code over time. We will certainly change ours. You don’t want to be able to see the source code we prov= ide but you will have a devil of a time keeping up if you make changes in SCSF = or IdeaBlade code.

Try to avoid that and be sure to track the changes you= feel you have to make. Please let = us know about those changes so that everyone can understand and benefit from y= our contributions.

Here is the new arrangement of the Infrastructure Vi= sual Studio Solution Folder:

Folder	Project<= /p>	Description<= /b>
Infrastructure. IdeaBlade	IdeaBlade.Cab. EntityModel	IdeaBlade assets in = support of business object models. Includes BrokennRules.
Infrastructure. IdeaBlade	IdeaBlade.Cab. Library	CAB-oriented UI supp= ort including base views and presenters, BindingSourceService, and = Grid= BuilderBase
Infrastructure. Scsf	Scsf.Infrastructure. Interface	SCSF interface asset= s that were originally generated into the Infrastructure.Interface project. This subset of those assets would be unlikely to change from one SCSF app to the next.
Infrastructure. Scsf	Scsf.Infrastructure. Library	All SCSF library ass= ets that were originally generated into the Infrastructure.Library project. They would be unlikely to change from one SCSF app to the next.<= /p>
Infrastructure	Infrastructure. Foundation	Your application spe= cific assets including resources, services, ListConverters, and application-specific base GridBuilder and view classes. They are particular = to Cabana now; you will change this for your application.
Infrastructure	Infrastructure. Interface	Your application Con= stants. Everything else was relegated to Scsf.Infrastructure.Interface.
Infrastructure	Infrastructure. Layout	The layout of the ma= in “card” in the Shell’s DeckWorkspace. The primary componen= ts in Cabana are the OutlookBarWorkspace on the left and the page DeckWorkspace= on the right.
Infrastructure	Infrastructure. OutlookBarWorkspace	The OutlookBarWorksp= ace from Matias Woloski. See below.
Infrastructure	Shell=	The application̵= 7;s “Shell” form and start-up project.

OutlookBarWorkspace

The former mysterious “CompositeUIExtensions.Winforms” project is now the more obvious “Infrastructure.OutlookBarWorkspace” (although it retains this original name for its Namespace).

The project is no longer flying under the “IdeaBlade” banner. We want to make absolutely clear that this = is a distinctive and highly valued contribution from Matias Woloski who deserves more overt credit than we gave him initially. There is a PDF in this project that references the original source and describes the changes we made.

The IdeaBlade assemblies no longer have a dependence u= pon this assembly; Cabana does, as seen in the Infrastructure.Foundati= on module.

GridBuilder Changes

The GridBuilder collection of classes have been revised to make it easier to accommodate similar versions of the same kind of GridBu= ilder. For example, you can now tweak the GridBuilder prototype instance of = the OrderG= ridBuilder to include or exclude the “Customer Name” column.

This was “useful” on the Customer page whi= ch does not need to repeat the Order’s Customer name in the grid (itR= 17;s always the same … the Customer shown in the summary above).

Of course it’s a bad idea to clutter a class with knobs and switches. One might have decided to create a separate GridBuilder class for this purpose, the CustomerOrderGridBuilder. So we created one and showed how it could inherit from OrderGridBuilder= and modify the columns after OrderGridBuilder was done.

CustomerPageController.AddServices() shows you how to= use either GridBuilder approach.

ControlViewPresenter Changes

ControlViewPresenterBase now has the ability to delay= the action of a View’s method call until certain pre-conditions are met.<= /p>

For example, some of the data bindings depend upon the readiness of the BindingSource. If the View called these presenter met= hods too early – before the BindingSource was ready – the bindings were dropped at runtime.

This meant that the View had to be aware of the Presenter’s initialization order, at least to the extent of calling s= ome presenter methods in the OnLoad. Such awareness is a bad co= de smell and we were able to sanitize it by enabling the Presenter to delay the binding until the BindingSource was ready. The View can call the method whenever it likes and the Presenter will get the timing right.

See ControlViewPresenterBase.DelayUntilBindingSourceReady= .

The mechanism is general purpose and, thus, adaptable = to other initialization order problems we may encounter in future.

Version 1.0.0.0

This is the first public release so there are no annou= nced changes between this and pre-release versions of Cabana.

Many of the features and behavior are the same as in Funhouse, the Cabana’s predecessor reference application.

One important difference is that all assemblies are co= mpiled into the “bin/Debug” directory off of the application root dire= ctory as in this illustration:

Funhouse Features missing in Cabana

Cabana has new features that were not in Funhouse and would have been difficult to add to Funhouse. Navigation is one example, the expanding and collapsing “Alerts” panel for Broken Rule display= is another.

On the other hand, many Funhouse features have not b= een ported yet to Cabana. Among the most important:

· Save

· Delete and undo

· Order managed list (the filtering of the Ord= er grid by order date).

· Employee filter by name or Id

· Login

These features will cross over soon.