This is just one of those things that is going to take a while to get used to.  Twice now I have lost significant amounts of time trying to track down a problem only to find out that it was a matter of my expectations.  I am so used to creating classes in VS2003 where classes are automatically public that it is not even something I think about.  So when I try to access a class outside of its assembly that was created in VS2005 I cannot figure out why the class is not found.

The reason is that the classes are now internal by default.  This means that they are only accessible by classes within the same assembly.  Most of the time I write code for the business and data layers of an application.  These classes are normally external facing so that the layer above them can use their functionality.  Because of this most of my classes should be public by default.  Only helper classes would be internal.

I understand why this was done, but after spending so much time in an environment that did the opposite it will take a while to get used to.