C#

using (ExchActions powershell = new ExchActions()) {
    ...
}

Luc Pattyn wrote:

lacking a sufficient number of decent questions since mediocrity introduced by QA started infecting the forums too.

Quote:

I'm disposing of "db" which should close the connection shouldn't it?

Quote:

I can try using but ...

public void Execute(IJobExecutionContext context) {
    int processedCount = 0;
    try {
        using (CloudPanelDbContext db = new CloudPanelDbContext (Config.ServiceSettings.SqlConnectionString)) {
            db.Connection.Open();
            using (ExchActions powershell = new ExchActions()) {
                var mailboxDatabases = powershell.Get_MailboxDatabaseSizes();
                db.StatMailboxDatabaseSizes.InsertAllOnSubmit(mailboxDatabases);
                db.SubmitChanges();
                processedCount = mailboxDatabases.Count;
                mailboxDatabases = null;
            }
        }
    } catch (Exception exc) {
        logger.ErrorFormat("Failed to ...");
    }
    logger.InfoFormat("Processed a total of {0} mailbox databases", processedCount);
}

db.Connection.Open();

Quote:

Behavior in EF6 and future versions

For EF6 and future versions we have taken the approach that if the calling code chooses to open the connection by calling context.Database.Connection.Open() then it has a good reason for doing so and the framework will assume that it wants control over opening and closing of the connection and will no longer close the connection automatically.

Note: This can potentially lead to connections which are open for a long time so use with care.

Quote:

You can use this property to interoperate with relational ADO.NET code.

The returned connection will be closed unless it has been explicitly opened by the user.

db.Connection.Open();

List<something> somename=new List<something>();

List<something> somename=new List<something>(someconstant);