Use of a Class library....common practice in VB.NET ?
Posted on 2009-04-14
I have taught myself VB.NET over the 2+ years with an extreme amount of help from EE postings. Wouldn't be where I am today were it not for EE.
I have 4-5 marketable apps that I am in the process of setting up a custom error trapping routine with and in my investigation regarding such, I found that one of the demos I downloaded has a class library included in it.
Is it a common practice to have a class library included in a solution that encompasses all of the classes you would incorporate in most, if not all, of your applications on release?
And are there any performance issues I should be concerned with in doing so?