Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Shouldn’t classes in DAL (customerDAL) be singleton? Since my controllers (customerController) exposes ‘Shared Subs’, then on every call, there is no need to create a new DAL object if already existed. Correct?
Thanks
Singleton objects are notoriously hard to test. I would look at creating your DAL in such a way that it isn’t expensive to instantiate and then creating a new one as needed. This way you’ll be able to write unit tests for DAL much more easily and still not incur much overhead. Additionally, if you create the DAL as a singleton, you’ll need to be much more concerned with making it thread-safe if you use it in a multi-threaded environment (such as a web app).