G
Guest
I am developing a new management system for my company, and with it have 3
layers of functionality written in VB.NET 2.0. In the business logic layer I
have a user class which contains all user information. I also would like to
put in a userCollection class for all my users. There are many other classes
like this on as well. However, what is the best way to do my collections? I
would like them so that a userCollection can only contain user items and so
on. I have seen that I could write my own collection class by inheriting
from the collection base. Would it be easier if I used generics instead?
The syntax is not correct but something like Private userCollection as
Collection(of Users) can this be done? If so, is it easier than developing
100+ seperate collection classes? How would I go about generics?
layers of functionality written in VB.NET 2.0. In the business logic layer I
have a user class which contains all user information. I also would like to
put in a userCollection class for all my users. There are many other classes
like this on as well. However, what is the best way to do my collections? I
would like them so that a userCollection can only contain user items and so
on. I have seen that I could write my own collection class by inheriting
from the collection base. Would it be easier if I used generics instead?
The syntax is not correct but something like Private userCollection as
Collection(of Users) can this be done? If so, is it easier than developing
100+ seperate collection classes? How would I go about generics?