Split Patterns up

The idea is to make it so that calls to Install-Package Patterns would still give you the same components, but that it would be a meta-package only. Patterns would break up into one project per root namespace, and an Autofac and Ninject flavor of each. At that point, Patterns dependencies can be expressed on a granular or global level, per preferences. This would allow calls like Install-Package Patterns.Configuration.Autofac, etc.

• Patterns
  • Collections - no dependencies
  • Configuration - System.Configuration reference
  • ExceptionHandling - Common.Logging
  • Interception - Patterns.ExceptionHandling, Castle.Core
  • Logging - Patterns.Collections, Castle.Core, Common.Logging, Patterns.Interception, Patterns.ExceptionHandling, System.Configuration reference
  • Mapping - AutoMapper
  • Reflection - no dependencies
  • Runtime - no dependencies
  • Text - no dependencies
  • MetaPackage
• Patterns.Autofac
  • Root (non-meta; convert to Patterns.Autofac.Core and keep Root as meta) - Autofac
  • Configuration - Autofac, Patterns.Configuration
  • Logging - Autofac, Common.Logging, Patterns.Autofac.Configuration, Patterns.Configuration, Patterns.Logging
  • Mapping - AutoMapper, Autofac, Patterns.Mapping
  • Modules (convert to Runtime) - Autofac, Patterns.Runtime
  • Sources - Autofac
  • MetaPackage
• Patterns.Testing
  • Configuration - Patterns.Configuration
  • Moq - Moq, Microsoft.Practices.ServiceLocation
  • SpecFlow - TechTalk.SpecFlow
  • Values - no dependencies
  • MetaPackage
• Patterns.Testing.Autofac
  • Moq - Autofac, Autofac.Extras.CommonServiceLocator, Microsoft.Practices.ServiceLocation, Moq, Patterns.Autofac, Patterns.ExceptionHandling, Patterns.Testing.Moq
  • MetaPackage
• Ensure all packages use minimal viable Framework version
• Recalibrate MyGet to push 4.0 CI builds, pointed at issue branch
• Verify correct package output via proof solution