Comments for Always Get Better

Comment on C#: Form.Close() vs Form.Dispose() by lellis

lellis — Wed, 05 Nov 2008 13:55:55 +0000

“Which to use? If you have no logic in the form’s close methods and don’t intend to re-use the form, go with Dispose(). Otherwise, go with Close(). Some programmers aren’t sure which to use, and they use both - Close() then Dispose()”

Actually, sometimes it is better to call dispose IF you have logic in the close event! For example, I have a form with logic in the closing event.
The logic just cancels the close. At some point, I *really* want to close the form, and the easiest way to do it is to call the dispose method. This
way I don’t need special logic in the closing event to deal with the special case.

Comment on C#: Form.Close() vs Form.Dispose() by James

James — Sun, 02 Nov 2008 22:11:59 +0000

In this case it makes sense to call both. Or call .Close() within a using construct. It allows the most graceful shutdown for a form, frees up resources right away, and suppresses the finalizer.

Comment on The 8 Month Mark by Allen Taylor

Allen Taylor — Sat, 16 Aug 2008 21:34:29 +0000

Nice writing. You are on my RSS reader now so I can read more from you down the road.

Allen Taylor

Comment on Internet Explorer URL Character Limit is 2,083 by Grokodile

Grokodile — Wed, 13 Aug 2008 01:14:26 +0000

Thanks!

You’d be surprised. We probably reject more blogs than we approve… and generally all we want is real blogs with real content written by real people.

Comment on Internet Explorer URL Character Limit is 2,083 by mwilson

mwilson — Wed, 13 Aug 2008 00:56:08 +0000

That’s certainly true. It’s cool that you Grokodile folks take the time to check out newly submitted blogs - you have a neat site!

Comment on Internet Explorer URL Character Limit is 2,083 by Grokodile

Grokodile — Wed, 13 Aug 2008 00:43:43 +0000

Microsoft is generally arbitrary and capricious…

Comment on C#: Form.Close() vs Form.Dispose() by mwilson

mwilson — Sat, 31 May 2008 21:00:33 +0000

Yes - Form.Dispose() does close the form. But it doesn’t call the Closing and Closed methods. If you have any code logic triggered by the form being closed, it will NOT be executed when the form is Disposed, unless you make a call to Close() first. Otherwise the form is just silently taken away.

Comment on C#: Form.Close() vs Form.Dispose() by NPT

NPT — Fri, 30 May 2008 17:32:47 +0000

“Form.Dispose() destroys the dialog and frees its resources back to the operating system. It does not call the form’s Closing() and Closed() methods. Once disposed, you may not recall a form.”

It certainly does Close the form. When disposing a form, it releases all resources that its using, including the resources keeping the form on the screen. Here’s an example…

using(Form f = new Form())
{
f.Show();

// Do some stuff
}

This will close AND dispose the form without ever calling Close.

Comment on How To Send Ctrl+Alt+Delete Using Terminal Services by Micke

Micke — Wed, 16 Apr 2008 19:25:32 +0000

Great tip, thanks!

Comment on Maintaining SQL Connections in ASP.NET by Always Get Better » Blog Archive » SQL Connections in ASP.NET - What you learned is WRONG!

Fri, 15 Feb 2008 19:23:15 +0000

[...] [This is a followup to: Maintaining SQL Connections in ASP.NET] [...]