programming languages
A recent user-submitted CodeProject article took an interesting perspective on the VB.NET/C# divide by proposing that the culture of Visual Basic is not conducive to professional software development: We’ve seen that the cultures of VB and C# are very different. And we’ve seen that this is
multithreading
As a follow-up to my caution about exceptions in Form.Paint(), I wanted to illustrate why this technique is so effective. Let’s say you had a form with this code: Private IsFirstPaint As Boolean = True Private Sub DoWork() Cursor = Cursors.WaitCursor StatusBar1.Text = "Loading..." System.Threading.Thread.
.net
Coming from humble Visual Basic 3.0 beginnings, by way of AmigaBasic, AppleSoft Basic, and Coleco Adam SmartBasic, I didn’t get a lot of exposure to formal programming practice. One of the primary benefits of .NET is that it brings VB programmers into the fold – we’re now real
vb.net
At a recent trinug user group meeting, Richard Hale Shaw was going off on a tirade about how Visual Basic 6 was “the ultimate anti-pattern.” I don’t disagree. VB6 had some serious issues, many of which .NET resolves. Then he put a question to the audience: “What specific things