This post originated from an RSS feed registered with .NET Buzz by Duncan Mackenzie. Original Post: Eric Gunnerson discusses grouping classes within an assembly... Feed Title: Code/Tea/Etc... Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind. Latest .NET Buzz Posts Latest .NET Buzz Posts by Duncan Mackenzie Latest Posts From Code/Tea/Etc...

Grouping classes in an assembly

This useful bit of information crossed my desk today:

When it comes to packaging in separate assemblies, remember that you pay a fairly large performance hit on an assembly load. An assembly should really be considered a unit of security control, independent versioning, or contribution from disparate sources. You might consider placing code in a separate assembly if it is used extremely rarely, but probably not.

continued in the full post...