In a previous post [https://www.johnpapa.net/blogs/john.papa/archive/2005/04/02/61096.aspx] I posed a question regarding how garbage collection operates on unused objects. Basically, once there are no more references to an object (let's say "x"), .NET sees that x is no longer used and

The using statement [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csspec/html/vclrfcsharpspec_8_13.asp] is another awesome tool that helps reduce coding effort and possible issues. An attentive reader added a good comment to my last post [https://www.johnpapa.net/blogs/john.papa

With VB 6 and ADO 2.x I can't tell you how many times I wrote the following type of code and only realized what I had done after I had pressed F5: The Infamous Infinite Loop Blunder '--- Using VB 6 and ADO 2.x oRs.Open Do While Not oRs.EOF Debug.Print oRs(0) Loop Usually the moment

Well, I finally did it. Today I joined the ranks of bloggers everywhere. I am grateful that the crew at codebetter.com was gracious enough to accept me into their community. Thanks guys! I'll be posting code samples, random thoughts, links, research and some personal musings in my blog ... that

I ran into a situation today where I wanted to know why ADO.NET’s DataSet.Merge method worked the way it did. Then it occurred to me that I could use reflection to find out. Using the Reflector [http://www.aisto.com/roeder/dotnet/] software found on Lutz Roeder’s site [http://www.aisto.com/roeder/do