Best practices on a couple of issues...

See more:

C#

WinForms

multi-threading

, +

Ok, so I have a fair bit of experience in doing ASP.Net pages in VB.Net. I am now working on a C# WinForms app. This app uses a SQLite DB for data storage. As I sit here programming it occurs to me that it would be a simple matter to open a connection to the database and leave it open for the duration of the application and make it available to all the classes to use. When doing web development this isn't practical because it is "stateless" and for most things you need a postback before you know whether or not you are doing anything with the database. So, I guess my question is, is it a good idea to have 1 connection for the whole winform app to use (with commands in each type to do the work)? If that makes sense? Do you winForm developers alway enclose a new connection with each method? e.g.

class myclass1
{
  public void doSomething
{
  SQLiteConnection conn = new SQLiteConnection(myString);
  conn.Open();
  SQLiteCommand cmd = new SQLiteCommand("someSqlStatement", conn);
  SQLiteDataReader reader = cmd.ExecuteReader();
  //loop and do work.
  conn.close()
}
}

class myclass2
{
  public void doSomethingElse
{//get another connection again
  SQLiteConnection conn = new SQLiteConnection(myString);
  conn.Open();
  SQLiteCommand cmd = new SQLiteCommand("someSqlStatement", conn);
  SQLiteDataReader reader = cmd.ExecuteReader();
  //loop and do work.
  conn.close()
}
}

Or alternatively you could pass the connection to each object in its constructor and then reference it directly:

class myclass3
{
  public void doSomethingEasy
{//use "globalConn" which was passed in the constructor
  SQLiteCommand cmd = new SQLiteCommand("someSqlStatement", globalConn);
  SQLiteDataReader reader = cmd.ExecuteReader();
  //loop and do work.
  conn.close()
}
}

Since my other question is pretty unrelated to this one, I'll post it separately.

Thanks as always!