Eddie Garmon's Weblog - All Comments

re: Cleaning the Visual Studio 2005 MRU list.

Tim Lenz — Tue, 12 Aug 2008 21:03:07 GMT

weblogs.asp.net/.../366825.aspx

Cleaning the Visual Studio 2005 MRU list.

Please fix the link or send me the source code please.

timothy.lenz@ va.gov

re: NUnit Template

AnonCoder — Tue, 22 Jul 2008 10:54:36 GMT

These links no longer work ... what happened to the templates?

Visual Studio Templates | devintelligence.com

Visual Studio Templates | devintelligence.com — Sun, 20 Jul 2008 14:44:48 GMT

Pingback from Visual Studio Templates | devintelligence.com

Link Listing - July 11, 2008

Christopher Steen — Sat, 12 Jul 2008 14:35:27 GMT

Link Listing - July 11, 2008

Christopher Steen — Sat, 12 Jul 2008 14:35:14 GMT

Link Collections Interesting Finds: July 11, 2003 - short edition [Via: Jason Haley ] The Morning Brew...

re: Cleaning the Visual Studio 2005 MRU list.

mbalasyam — Wed, 02 Jul 2008 01:45:58 GMT

the file is not found there.

re: Synchronization, ReaderWriterLockSlim, and Lambdas

UltimateRinger — Tue, 01 Jul 2008 13:03:21 GMT

Richard, I see your point. Generally if an exception occurs in either of the manner you speak, then letting the exception bubble is the proper course. Given my last change, I do need to release the lock, thanks.

re: Synchronization, ReaderWriterLockSlim, and Lambdas

Richard — Mon, 30 Jun 2008 18:04:31 GMT

The code in the catch block only needs to be executed if there is an error creating the SynchronizedEnumerator instance. In all other cases, the SynchronizedEnumerator takes over responsibility for calling Dispose on the synchronizedReader instance.

Adding a Guard statement to check for a null argument will prevent some errors, but not all. For example, the getEnumeratorFunction may throw an exception, or there may not be enough memory available to create the enumerator or SynchronizedEnumerator instances.

re: Synchronization, ReaderWriterLockSlim, and Lambdas

UltimateRinger — Mon, 30 Jun 2008 14:13:16 GMT

Richard, the problem was with in the using in general.

I also found another condition when trying to write while doing a long enumeration. The code has been updated.

Also, your catch block will never get executed unless there is is an error actually getting the enumerator, therefore I added back in the Guard statements that were removed.

Interesting Finds: 2008.06.30

gOODiDEA — Mon, 30 Jun 2008 00:26:58 GMT

WebCSSLayoutCheats.NETSynchronization,ReaderWriterLockSlim,andLambdasCodeComment.NETC...