Personally, without checking the other comments first to bias my opinion on, VB.NET isn't THAT bad, but I still don't like it. VB.NET was my first programming experience. It was the first language I learned about 6-7 years ago, and I did my fair share of initial learning how and why things were as they were in it. Eventually, both from peer pressure and pure interest I started to experiment with C#, and fairly quickly I started really liking it. It just felt more logical to use curly brackets to mark down your code instead of new lines and verbose words, but I also remember back then (could've been me, it was my first programming experience after all) that when I ran into problems with VB.NET and tried rewriting the project in C#, it worked better in C#, without the flaky behavior. Now before all of you are going to yell "But MS IL! That's impossible as it gets compiled to the same bytecode anyway!" there's still 2 different compilers here, one for C# and one for VB.NET, and perhaps the syntax gets translated differently? Anyway I'm talking about 6-7 years ago here, back then .NET 2.0 was the new kid on the block and perhaps MS has fixed things since then. But personally, even though VB.NET was my first language, I really prefer C# between the .NET languages. And I also tell everyone who's doing VB.NET to at least try to get acquainted with C#. Why? Well, C#'s syntax is much less arcane than VB's, and can prepare you for maybe trying C or C++ some day. After all, framework languages are cool and all, but in some businesses, those low level languages really are where the party's at. So if you really want to do .NET, why not do the most widely used, least arcane one?

Despite me personally not liking McAfee, it has nothing to do with it. Hooking network level stuff in Windows at such low level is really nasty and hacky usually. Especially if you want to keep it compatible with windows XP. I've seen this 'no traffic allowed, even DHCP' error happening with everything from Norton to F-secure to Kaspersky to ZoneAlarm. Usually fixes with a complete reinstall of the software.

..Did you guys just have a non-flaming argument that involved Apple AND Microsoft? :wtf:

I personally really hate the error GDI throws whenever anything goes wrong. "A generic error has occured in GDI+". Like, 'You don't say' much?

I personally really hate the error GDI throws whenever anything goes wrong. "A generic error has occured in GDI+". Like, 'You don't say' much?