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

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

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

Here’s a quick quiz about GC: Q) At what point is x eligible to be cleaned up by the GC? <FIELDSET><LEGEND>Garbage Collection</LEGEND> public void foo() { Class1 x = new Class1(); Class2 y = new Class2(); y.Width = x.GetWidth(); y.Height = y.Width; y.Color = "Red&quo

Quick blog for now … I set up a new ASP.NET project, turn on NT auth, turn off anonymous access, write some ADO.NET code to connect to SQL Server via integrated security and viola! I get this lovely error: <P></P> <FIELDSET><LEGEND>Arg!</LEGEND> <H2>Login failed