I sure didn’t know anything about this site until I started hating OpenDNS. What happened to my Google feeling lucky thing? No clue, but this fixes it!

ECMA

ISO

W3C

I feel like I’m missing one or two.

Additional References:

Document Center
IHS/Global

OK, this will NEVER be totally valid but here goes. 5 CSS “Hacks” to Help You Stop Using Images.

I wasn’t aware of this one until I visited Jon Skeet’s site again.  Very readable assuming you have a bit of knowledge of “language speak.”

Speak of Jon, here’s his FAQ from the mplc (microsoft.public.languages.csharp) newsgroup.

C# Language Specification – I feel like I’ve posted this at least 3 times. My wires get crossed very easily sometimes.

XML Documentation Comments

I just found this a bit funny is all.

The simple tutorials are REALLY simple, as in too simple.

The intermediate are like simple^3.

Then advanced makes leaps so high you literally have to be versed in TONS of the language specification.

Anyway, low-bandwidth version rocks!

http://msdn.microsoft.com/en-us/library/aa288436(VS.71,loband).aspx

Also, C# Programming Guide.

Jochen Kalmbach a Visual C++ MVP has this useful utility for us.

This basically boils down to garbage collection I believe.  Mike Dimmick bluntly states if it can be disposed, dispose it.

So for example as I instantiate subclassed forms for things like about pages, options, and so forth I should call dispose in that same context.  For example:


// Instantiate new object of user-defined About class (subclassed System.Windows.Forms.Form)
About aboutForm = new About();

// When About is closed, explicitly dispose of it
// to free up memory and prevent memory leaks.
aboutForm.Dispose();


Then this comment struck me… should I be using managed code for something this simple? On one hand I’m thinking I don’t know nearly as much as I should and this probably doesn’t even apply, then again, I simply have no clue at the moment.

Then Chris Lyon’s summarization seemed to shed light. When you call Dispose it does not mark it for garbage collection but rather “unloads the object’s (unmanaged) resources from memory.”  Chris’s article needs serious reading as do the links he links to.  Why?  Dispose is not thread safe which means actions can be perfformed on it synchronously causing catastrophic results.

Jesse Liberty recommends implementing the IDisposable interface (as do some of the other articles referenced) but what I wonder is if it is necessary in my situation.  I’m still thinking not but having no clue at this point.

The Stack Overflow link shed much more light on the subject.

Oh, I forgot one last thing.  Using a using block explicitly calls Dispose.  I read this elsewhere, but reading this by the C# guru Jon Skeet reminded me of it.

References:
http://mikedimmick.blogspot.com/2006/08/you-must-call-dispose.html
http://weblogs.asp.net/pwilson/archive/2004/02/20/77435.aspx
http://blogs.msdn.com/clyon/archive/2004/09/21/232445.aspx
http://ondotnet.com/pub/a/dotnet/2002/02/11/csharp_traps.html
http://stackoverflow.com/questions/628752/why-call-disposefalse-in-the-destructor

PEOPLE:  Please bear in mind these posts are not for you.  If you find them useful, yay, otherwise they are my ramblings to help keep notes on things I cannot remember.

http://www.templatelite.com/

http://www.templatelite.com/60-photoshop-illustrator-tools-and-tutorials/

I guess Becca Wei of Beccary.com never came back. So in the meantime you can find a few of her themes here and here.

Here’s the last thing I found related to her.

Web Archive