I added a graphic of the solution layout of the High Ball Application with some basic descriptions of the various sections.  I do want to however reduce the number of projects inside the solution, but for now I've left it in the very separated out way I initially created the solution.

My next idea is to get some initial views done to use as a starting point for functionality.  I'd like to complete the security administration section soon, so the other parts of the application can be further fleshed out.  I will admit though, I'm not 100% sure how I want to setup the security, and am currently brain storming the idea.  If anyone would like to jump in on that lemme know.

Sometimes I want to use the enterprise library, but just not all 200+ MB of the thing.  So I go about piecing together the pieces I want, by project, into the main solution.  This can be troublesome as all the pieces don't just drop in simply.

First Bump in the Road :: GlobalAssemblyInfo.cs

The first problem I've run into this time around was the GlobalAssemblyInfo.cs file wasn't available.  After fiddling around a minute I realized this needed to be added to the solution at a global level.  The way to do this is to right click and add existing file to the actual Solution.  Unfortunately I had statically added a copy of this file to my projects I was adding and simply re-added those projects with the appropriate file mapping again.  Note to self, "If adding individual blocks from the enterprise library make sure to add the GlobalAssemblyInfo.cs file first and then the individual blocks".

Second Bump ::  The "Common" Project

The common project is used in pretty much every single project in the enterprise library solution.  For some reason when I added all my projects, the common reference went away in numerous projects.  So this was a case of just adding the reference back to several of the projects.  Maybe I shouldn't add them this way, but regardless, it gets the job done.

So far I'm now up and running, but just wanted to present a searchable note about these bumps I've hit.  Once these things are resolved the library blocks are flawless.

I've finished what I wanted to of my basic diagrams.  I need to add the description of what I am trying to do now to elaborate what exactly the brain storming diagrams entail.  The following are the remaining brain storming diagrams that I've come up with that will at minimum, get my pet project started.

What I've done in each of these is prepare them, or complete a further sub-level break down of the primary modes for a particular mode type.  For airplane travel there is the break down into commuter, small aircraft, etcetera, and then the further break down to the specific Airbus, Boeing, or Beech Hawker Craft.  At some point the sub level data would probably be stored in a database but this is just brainstorming, so I'm just drawing simple correlations at this point.  The next step is to start breaking down specific elements, or scope, of what exactly my first application with this topic.  I have some initial elements for the design, some ideas for other particular applications involving scheduling, seating arrangements, etc.  I will move forward on this shortly and have an actual documented scope that I will start building to.

Here's one of the first brainstorming diagrams I've come up with.  It's a break out of transportation modes.  I wonder if I've missed any?  Each mode is broken out to the amount of persons the respective mode can carry.  This information will then be broken down at some point.  Right now I'm off to some lively debate at Life of Riley's (it's in Portland, so if you're here, come and have a drink).

• Original Brainstorming Visio File 
• Original Brainstorming PDF File

So I've been planning to start a project on the side, just for fun, that I could really showcase some of my interests and skills all at the same time.  In other words, from a high level, all the way down to the nitty gritty example, build a fully functional application.  I got to thinking, what really truly interests me enough to stay focused on to develop an application for that I could use to present enterprise application demos with?

Well, I've kind of shut my "Transit Slueth" blog down for the time being, maybe permanently so what better topic to use. With that in mind I will be posting some brainstorming diagrams and other ideas on what I intend to develop.  It will be related to transit in some way, but I'm not 100% sure yet.  Feel free to pop ideas in the comments section.  Until then I'm off to brainstorming a problem to create a solution for!  (It's kind of funny, I usually don't create the problems, I just create the solutions!)

There are rules engines, business processing engines, and all these other engines.  After spending years working on these engines I figured I would sit down and create a Transit Engine.  If you read any of my other blogs or know me personally you know why I've decided this is something I want to create.  There are however other reasons.

One of the main reasons for creating this project is that I want to have something to provide as a web portfolio, interface portfolio, coding patterns, and all those cool things I learn how to do portfolio.  All too often I don't feel I have a good reference point for what I've done.  With nothing more than my mere promise to customers I've often felt uncomfortable expecting trust.  With immediate reference point I have a little bit more for them to go on to find that customer trust.

I'll include all of the project's documents ranging from UML Diagrams to actual code implementation along with some good ole' unit tests for good measure.  Of course all the documents won't get dumped out here on the site at one time, it'll take me a little while to accrue all of the pertinent items.  I will provide step by step instructions for where I'm heading, what I'm attempting to acheive, and the intended or unintended results of the project goals.

With all that done - I'm getting started.