title: Making code internal but available for unit testing from other projects
body: <p>We put all of our unit tests in their own projects.  We find that we have to make certain classes public instead of internal just for the unit tests.  Is there anyway to avoid having to do this.  What are the memory implication by making classes public instead of sealed?</p>