/*

Typically when I create any framework, I always create a console application for that framework simply 
for debug and testing purposes.

Some people much prefer to use a utility called NUnit for their testing and that's definately a much 
better tool for testing base functionality of components, but as a framework designer it's critically 
important that I write how I'm going to use the framework because I create the framework (for a detailed 
discussion on this design method see /Includes.js.aspx.cs in the SampleWebsite).  Using a console 
application allows me to maximize the usability of my frameworks as well as test the output as though 
I were an actual user of my framework.  It also makes people testing my framework happier as they now 
don't have to write their own application base to test my framework.

Also, using a console application for my data analysis is often much more efficient than creating and 
using a mock website to look at my data.  Tabular data is definately an exception, but a side from 
that, analyzing scalar values and analyzing services is so much easier to do with a console application 
than with a website, a winform, a WPF application, or another service.

*/

using System;

namespace SolutionConsole
{
    class Program
    {
        static void Main(string[] args) {
            Console.WriteLine("Done.");
            Console.ReadLine( );
        }
    }
}