Hi,

I am a software developer, I am working with visual basic since last 4 years and now looking to upgrade my skills to .Net
Since it is just a beginning for me with dot net. I use to use Microsoft’s website for reference. But, whenever I visit the site, I find something coming new everyday

Earlier it was just .Net then, I found .Net 2003 and now it’s .Net 2005, I am confused now, how can Microsoft change the things this frequently. This is also cause of worry for me and I think everyone who is like me. So anybody there who can explain me what’s this all about and how can I cope with such frequent changes


Vinod Pawar

__________________
Vinod Pawar
United States

Ha, yes, I see what you mean. Things are following each other up in rapid succession.

Only today I noticed that Microsoft released a series of Visual Studio .NET 2005 Express betas targeted at non-professional programmers / web developers. It may take a while before the final versions are released (mid 2005), but it's a god indication of what is coming. The same applies for professional version of VS.NET 2005.

Personally, I am not too worried about these new versions. I try to see things as a evolution rather than a revolution. This means that many of the things you pick up from .NET 1.1 will carry over to .NET 2 and Visual Studio .NET 2005. The things you're learning now are *not* a waste of time; they help you understand and build applications now, and in the future.

If you need to focus on something, focus on .NET 1.1. If you ever get the chance to choose between 1.0 and 1.1 for application development, you should always choose version 1.1, so it's best to concentrate on that version. The changes between 1.0 and 1.1 are not that big though; that's why it's only a dot release, not a full and new release. If you understand one, you'll also understand the other.

But I understand your frustrations. There is so much to learn, yet so little time. It's impossible to learn and know it all, so you have to concentrate on a number of areas and try to specialize. If you have been working with "classic VB" (isn't that a frustrating name after spending 4 years mastering it), you shouldn't have too hard a time "upgrading" to .NET. Many things are still the same, but you should realize that of course many things a re different as well.

They only way to prepare yourself is read read read. There are a million books and Web sites that target .NET. Get a few, read them and try to understand the general concepts of the .NET framework. Once you do, you'll find that many of your "old skool principles" will carry over seamlessly to the .NET world.

Hope this helps a bit,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: 02 - Avon by Queens of the Stone Age (Track 2 from the album: Untitled) What's This?

ALWAYS remember- MSFT is in business to make money. If they don't constantly change and upgrade no one will have a reason to spend money on MSFT products.

MSFT seems to try to have a 2 year cycle for each new release of tools. (1.0 and 1.1 were closer). It seems like a "long time" - 2 years.. but, since adoption is slow- it could be months after you get started with a tool before they upgrade.

As Imar says, ignore 2005 for now. I have the Technology Preview installed here somewhere- I think I started it once. I'll keep it around (and updated) to - hopefully- play with some of the new stuff as it gets announced and (pehaps?) I'll convince Wiley to let me do some technical reviewing for the 2005 books..

Either way, Focus on 2003 and 1.1 of the framework.

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

thanx Imar, Hal Levy



Vinod Pawar