I'm rewriting an app, and am starting to worry about long term performance of the way I'm writing it. First, a little background, and please read all of this because I think it all comes into play. Google EE Linkers need not apply.
I'm using Subsonic as my DAL, and subclassing it for the most part. I'm trying to avoid using their collections within the page classes (although sometimes that's just so easy it's sick!), and wrapping things in my own DAL (as seen below).
Getting to my questions,
1.) When I return a DataSet, how is that destroyed? Does the GC come by at the end of the page and wipe all that up? If so, is it something I can rely on, or is it like ASP Classics, "Oh, we close all connections so you don't have to *wink wink*?
2.) Same thing with a DataView, and would it be better to return the dataset and work with that, or is it roughly equivalent
3.) Same thing with SubSonic COLLECTIONS
4.) Any recommendations on making my DAL a little leaner, meaner, and extensible?
Points will be awarded to those who
a.) Link me to PRECISELY what I'm looking for
b.) Engage and really try to understand what I'm trying to accomplish.
I've asked these types of "theory" or best practices questions before, and have been consistently disappointed with the Interaction. I would really like to LEARN here, not just quick fix, and not with people randomly linking me garbage that doesn't really apply (the quick points people).
Thanks in advance.
public class StatusControl
public static DataView GetAllStatus()
DataSet ds0 = new DataSet();
IDataReader i1 = SPs.SelectStatusAll().GetReader();
DataView dvView = ds0.Tables.DefaultView;