Comments on: Visual Studio 2005 – Make new classes public by default

By: David Dobbins

David Dobbins — Mon, 25 Jun 2007 12:06:50 +0000

Ah, I was relying on the “…all nonpublic types in an assembly are visible to another assembly” that is stated on the page documenting the attribute itself: http://msdn2.microsoft.com/en-us/library/system.runtime.compilerservices.internalsvisibletoattribute(VS.80).aspx

My (very limited) testing so far indicates that privates do indeed remain private.

By: Jason Meridth

Jason Meridth — Mon, 25 Jun 2007 09:39:00 +0000

Thank you David.

This will by no means remove the need for mocking.
According to the MSDN information:

http://msdn2.microsoft.com/en-us/library/0tke9fxk(vs.80).aspx

“…private types and private members will remain inaccessible”

By: Joe Ocampo

Joe Ocampo — Sun, 24 Jun 2007 23:02:14 +0000

Very nice find.

By: David Dobbins

David Dobbins — Sun, 24 Jun 2007 20:31:03 +0000

Although I haven’t yet had the opportunity to try the “friend assemblies” feature (InternalsVisibleToAttribute), it looks to be well suited for this.

By: Jason Meridth

Jason Meridth — Sun, 24 Jun 2007 19:53:55 +0000

Don’t get me wrong the reason I make my classes public by default is that I practice Test Driven Development (TDD) and for NUnit to see my Test Fixture it has to be public.

Before any of you starti commenting on class exposure. =)