Geeks With Blogs
CodeSeeker Just another developer trying to do the right thing July 2007 Entries
Parallel development using Visual SourceSafe 2005
An additional, subtle, yet profound change I made for my group when I upgraded us to Visual SourceSafe 2005 (VSS) was to change the work style from Lock-Modify-Unlock (the default work style for older versions of SourceSafe) to the Copy-Modify-Merge work style. This might seem like a small difference, but let me explain what that means. With the Lock-Modify-Unlock work style, developers check out a file, then work on it, then check it back in to VSS. While the file is checked out, no one else can ......

Posted On Friday, July 27, 2007 9:22 AM

Software Process Improvement from the ground up
My group is pretty immature as far as anything like CMM(I) goes. We are only a couple steps ahead of complete chaos, which is pretty darn bad. So how do you get from chaos to order? What are the first steps to take? I'll speak from my own experience over the few months that I've been in this group. A little history: at my last job, the process was more mature. There was only one project, a large one. It was managed pretty well, and everyone was working on the same codebase with the same tools, etc. ......

Posted On Wednesday, July 25, 2007 4:28 PM

Which is better, C# or VB?
The age-old question. And the first answer should always be: "Yes." Because they both use the same .NET Framework classes, they both compile to the same intermediate language, and there is functionally no difference between the two. Syntactically, they are different, but they can both do the same things. That being said, I will admit that I have a bias towards C#. I am currently working in VB, but that's not completely by choice, that's just what my current group uses. I like that because I'm learning ......

Posted On Monday, July 23, 2007 11:26 AM

Short-circuit IF statements in VB.NET with AndAlso
In-line checking of values during the evaluation of a compound IF statement in VB.NET can be done as a way of "short-circuiting" the IF statement in case further evaluation might cause errors. For example, Dim blah As Nullable(Of Integer) = Nothing If blah.HasValue And blah.Value < 5 Then Console.WriteLine("Something really important") End If In this case, the IF statement will cause an error. The AND operator in VB causes all clauses prior to the THEN statement to be evaluated. So both the "blah.HasValue" ......

Posted On Monday, July 23, 2007 9:03 AM

Copyright © Mike Ellis | Powered by: