Pro Silverlight 5 in VB

Class Library Assemblies

So far,  the examples you've seen in this book have placed all their code into a single assembly. For a small or modest-sized Silverlight application, this straightforward design makes good sense. But it's not hard to imagine that you might want to factor out certain functionality and place it in a separate class library assembly. Usually, you'll take this step because you want to reuse that functionality with more than one Silverlight application. Alternatively, you may want to break it out it so it can be coded, compiled, debugged, and revised separately, which is particularly important if that code is being created by a different development team.

Creating a Silverlight class library is easy. It's essentially the same ...