.NET Question Time
Ahmad: For many, the term “.NET” sends chills down the spine. How would you answer the question: “What is this .NET thing?”
Karl: I suppose it all depends on who’s asking. If my Aunt Mable were to pose the question, for example, I’d have to first explain that someone invented a typewriter, and we’ve since evolved onto something called a computer, which has something to do with this thing called “.NET”.
But for the knowledgeable people at DEVpapers.com, I’d say that it’s one of those broad Microsoft visions based on “distributed computing”. To developers, it really means two core products – the free .NET Framework, which is like one big, intelligent runtime, and Visual Studio .NET, which allows you to write code that runs on top of the .NET Framework.
I agree that it’s a little scary at first. I found that out, alrighty. But it’s easy to overcome with just a little patience!
Ahmad: I understand .NET it works with many different languages. Which is the best to learn?
Karl: The latest version of Visual Studio .NET supports four different languages by default: Visual Basic .NET, C#, J# and Visual C++. In general, if you’re a Visual Basic developer, go for VB .NET; if you’re a C++ developer, opt for C#; if you’re a Java developer, check out J#.
The core functionality of the .NET Framework (the “runtime”) is accessible by any language and the differences between each are so minute, it makes sense to go with the one whose syntax you know best.
Ahmad: You teach a lot of people how to move to .NET, but how did you do it? And do you really recommend it?
Karl: Oh, it wasn’t an easy ride. I just dived in when they released the early beta versions and felt the cold, cold water. I spent months playing around and then wrote about what I discovered. And I’m still learning: to this day, I’m still picking up tips and tricks to make my development work better.
And no, I don’t recommend it for everyone. Just because I use .NET and it works for me, doesn’t mean it’s going to “do it” for everyone. But it’s certainly an option worth investigating. With a little time and effort, it can bring some interesting rewards.
Ahmad: So then, what are your favorite .NET features?
Karl: Undoubtedly, ASP.NET. This is like the next version of ASP, and it allows developers to build interactive Web applications almost as though they were simple Windows programs. The deeper you get, the more you realize how you can extend it too – and really add power where you want it.
But don’t get me wrong. I’m not one of those 100% .NET evangelists. My books regularly highlight Microsoft mistakes and clearly point out bugs and pitfalls. There are some things I really dislike about .NET – the inability to edit code during runtime, for example, a great VB 5/6 attribute.
Ahmad: If I understand, ASP.NET isn’t a language, right?
Karl: That’s correct. ASP.NET is a part of that .NET Framework “runtime” I mentioned. You can write code for ASP.NET using VB .NET, C#, whatever.
Ahmad: I see. And what about those coming from VB 5/6 to VB .NET? Is it worth upgrading? What are the differences?
Karl: There are hundreds of differences, some good, some bad.
On the plus side, you’ll have access to dozens of fresh controls. You’ll be able to plug into the many functions of the .NET Framework to help you get your work done. You’ll be able to create some of the newest types of applications, such as ASP.NET Web sites, Web services, and applications that run on anything from mobile phones to PDAs. Your code and its resources are also “managed” by the Framework, meaning no memory leaks or other such errors will occur – all the plumbing is handled for you.
But there’s a downside too. Your clients need the .NET Framework installed in order to run your program (about 20MB, yet is now being distributed with all versions of Windows). You also need to get your head around a few syntax changes, plus figure out the main classes within the .NET Framework. It just takes time – and a good book or two.
Also, as a general rule, don’t upgrade existing VB applications using the built-in upgrade wizard. It’s not efficient and is suited only to smaller applications. My advice: don’t take the upgrade route, use .NET for new projects only.
Ahmad: Have you tried Everett yet? That’s VS .NET 2003, right?
Karl: Yup, “Everett” was the codename for pre-release Visual Studio .NET 2003. I spent ages working with it (the final version was released in April).
Ahmad: So, is it any good? A major advance over VS .NET 2003?
Karl: There’s a lot of hype surrounding VS .NET 2003, but the truth is that it’s not all that different from VS .NET 2002.
I have the final version on my machine and the only real additions are the J# language, built-in support for mobile and ‘smart device’ (PDA) projects, plus an obfuscator to protect your code (which is freely downloadable anyway). There are a few bug fixes, user interface changes and small syntax additions too, but nothing major.
I’m guessing that’s why the upgrade price for VS .NET 2002 users is only around $30.
Ahmad: Does .NET mean the end for PHP?
Karl: Oh yes.
Just teasing – of course not! From my experience, PHP is serving a different sort of market. Yes, it overlaps with ASP.NET – and yes, in future, new developers may opt for the easier “drag and drop” method of ASP.NET development over scripted PHP.
But I don’t think there’s any imminent threat. You are a drama queen, Ahmad.
Ahmad: I know. You should see my stockings.
