Identify problem with nested namespaces

- I organize my migrations with my mappings, so that my FluentNHibernate mapping and my migration each share a namespace inside the main migrations namespace or project
Match migrations found in nested namespaces

- No need to call GetExportedTypes() again, or to check if it matches the convention, as that was already done.
- Instead, just filter the list to those whose namespace is an exact match, or start with the match plus a dot
- Makes it so Foo.Bar matches types:
  - Foo.Bar.Migration1
  - Foo.Bar.Nested.Migration2
  but not:
  - Foo.BarBaz.AnotherMigration
Remove the public setter for VersionTableMetaData on VersionLoader

- The setter gave the impression that it could be used. However, the version migrations are triggered in the constructor, so changing the metadata has no effect other than causing later confusion.
- To use something other than the default, you have to have a type in the migration assembly that matches the convention for selecting the version table metadata.
Merge pull request #136 from tgmayfield/RemoveSetterForVersionLoader.VersionTableMetaData

Remove the public setter for VersionTableMetaData on VersionLoader

Thanks!
Finding migrations in nested namespaces should be optional

- Made setters on MigrationLoader private, as changing the properties will have no effect
Merge pull request #135 from tgmayfield/LoadTypesInNestedNamespacesWhenNamespaceRestricted

Load types in nested namespaces when namespace restricted
Added a better fallback mechanism for connection string name

ref #134
Added some empty tests for config fallback order
Added InternalsVisibleTo attribute to AssemblyInfo
Moved tests
publicized NetConfigManager

apparently the InternalsVisibleTo attribute is kind of ugly with strong named assemblies
Added some test fixtures
filled in some tests, added fixtures
Added more fixtures

some of those app.config files with their respective .exe files
All tests pass

fixes #134
Merge pull request #137 from tkellogg/fallback-order

Fallback order for ConnectionStringConfigPath
Moved NetConfigManager to ConnectionStrings
Issue #63 ICreateForiegnKeyCascadeSyntax typo in foreign
Extension to Execute to add new method WithDatabaseType
Update packaging.rb to create Nuget package

- Updated rakefile to build the release in .NET 3.5 (not 4.0)
- Updated packaging.rb to create a nuget package with the same
  contents as the current Nuget package. Except for the vshost files.
  Version can be set two ways. Either change it in packaging.rb or
  use the version variable from the commandline. The nuget package
  is created in the nuget directory. A new Nuspec file is also
  generated every run.
  To run: rake nuget_package version=0.9.0.2
  or with the default version: rake nuget_package