OK, enough negativity. Here’s an idea I had to help me with my unit testing – tell me what you think:
I have a test for every class I’m testing that gets the count of the public members, and I compare that to a known value I store as a constant in my test class. Then, every time I add a member, I increment the value. If I forget to increment, I get a red light. It provides me with a check to help ensure that I add the test.
Here is the code I use to get the member count:
ClassBeingTested classBeingTestedInstance = new ClassBeingTested();
Type type = classBeingTestedInstance.GetType();
Assert.AreEqual(ExpectedCountConstant, type.GetMembers().Length);
Now, I know that this would be unnecessary if I could actually do test first, but I’m not there yet. I’m trying to get there – baby steps. I think this technique is a good sanity check to help me move along the path.
It never ceases to amaze me how many times I see people spell “Allot” wrong. They leave out the second “L”. And the sentence never really seems to make sense, either. I guess it’s a case of a spelling error and a grammar error? J
How convenient – someone posted a list of people not willing to keep up with the Microsoft treadmill… J
Seriously, I agree with Geoff. There are plenty of resources, and anybody who is working with VB6 knows all of the workarounds, or can easily find them (I’m pretty sure Google was around when VB6 came out, right?).
Don’t get me wrong; even though I have completely turned my back on VB (I’m a C# convert), I owe my livelihood to it. I never would have gotten as far as I have without spending 8ish years working with VB in its various incarnations. But really, the transition from VB6 to VB.Net isn’t that difficult, if you actually write VB6 code. The problem I think is that most people still writing “Classic VB” write VB3 code, which doesn’t make for an easy transition.
Just because Microsoft is dropping support doesn’t mean you can’t use the tool. I like the idea of open-sourcing it, though. Then, companies will spring up to handle support, and Microsoft can wash its hands of it. Well, except that I can’t see any company making any money doing it.