BluePineNeedles - Professional Profile

Action

Author

Authority

Debator

Editor

Enquirer

Organiser

Participant

If Owner

Member Types

Have no restrictions on voting frequency

silver

Bypass spam checks when posting content

silver

gold

SubEditor, Mentor, Protector, Editor

Store personal files in your account area

platinum

SubEditor, Editor

Have live hyperlinks in your profile

bronze

silver

SubEditor, Protector, Editor

Have the ability to include a biography in your profile

bronze

silver

SubEditor, Protector, Editor

Edit a Question in Q&A

silver

Yes

SubEditor, Protector, Editor

Edit an Answer in Q&A

silver

Yes

SubEditor, Protector, Editor

Delete a Question in Q&A

Yes

SubEditor, Protector, Editor

Delete an Answer in Q&A

Yes

SubEditor, Protector, Editor

Report an Article

silver

SubEditor, Mentor, Protector, Editor

Approve/Disapprove a pending Article

gold

SubEditor, Mentor, Protector, Editor

Edit other members' articles

SubEditor, Protector, Editor

Create an article without requiring moderation

platinum

SubEditor, Mentor, Protector, Editor

Approve/Disapprove a pending Question

Protector

Approve/Disapprove a pending Answer

Protector

Report a forum message

silver

bronze

Protector, Editor

Approve/Disapprove a pending Forum Message

Protector

Have the ability to send direct emails to members in the forums

Protector

Create a new tag

silver

Modify a tag

silver

"Using" statement

BluePineNeedles10-Feb-05 13:01

BluePineNeedles

10-Feb-05 13:01

Today I discovered the using statement in C# (it's amazing all the things they have built in to C# that are just completely absent from VB.Net).

Dude, this using statement rules my world!
Here's the gist:
Tired of the following?

SomeDisposableResource x;
try
{
   x = InstantiateX();
   UseX(x);
}
catch (Exception ex)
{
   throw ex;
}
finally
{
   if (x != null)
      x.Dispose();
}

I sure as hell am.
I want my resource consuming variables to dispose of themselves as soon as they fall out of scope. I'm a fire-and-forget kind of guy. That's why I gravitated toward a managed environment (I love garbage collection).
I stumbled across this little gem that solves my problem.

using (SomeDisposableResource x = InstantiateX())
{
   UseX(x);   
}

The compiler knows to dispose of x as soon as it falls out of scope, even if it is because an exception is raised. This rocks my world, and is another reason I can't live without C#.

First stumbled across this here[^].
Much more detail here[^].
Statement is deconstructed here[^].

-- Being innovative means not being afraid to get fired.

Experience my frustration (AKA problem solved)

BluePineNeedles10-Feb-05 12:29

BluePineNeedles

10-Feb-05 12:29

Here is what has caused me headaches since the beginning of time!
I want to serialize a custom collection that I have created. That collection has an event that is raised when an item is added (good for GUI event concurrency). That event causes the collection to not serialize because the event subscribers are not serializable. I cannot apply the NonSerialized attribute to the event, because .Net will not let me.

Grr.

After what seems like a gazillion years writing stupid ISerializable implementations, I have discovered the solution. Like mana from heaven, the clouds open up and... Problem Solved[^].
Thank (G/g)od for [nearly] undocumented features.

[field: NonSerialized] here I come!

-- Being innovative means not being afraid to get fired.