Hi All, 1) Is this true:- More methods (i mean public) and variables in classes will make the application slower when instances are created? How to design methods in classes? How many methods can we normally have in classes for performance reasons? I read somewhere that classes must not be too big or too small.
Can we find out how the classes are performing, faster or slower? What if I make the methods as static(C#) so that I don't create any instance of the Classes at all? (These methods can also be database access methods) 2) I have Data Access Layer(DAL) classes and I am passing DataSet as arguments. What are the other ways of passing Rows of records to DAL, so that the processing will be faster? Can anybody help me to understand this? thanks in advance for the OOPS gurus! Mohan Disclaimer: The contents of this e-mail are strictly confidential and may be privileged. It represents solely the views of the author and is meant only for the stated recipient/s. Any unauthorized distribution is strictly prohibited. F J Benjamin Group or its subsidiaries will not accept responsibility for any damage caused by this e-mail or attachment/s (if any), which have been checked for viruses. Please visit our website http://www.fjbenjamin.com ------------------------ Yahoo! Groups Sponsor ---------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM ---------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
