With the cnahge from VB 6 to .NET 1, now .NET2, are we going to have to learn all over again to program under WinFX
I'm just now getting my bearings in VB2005 (from VB5 Pro), will this be obsolete in a few months as well
Am I misunderstanding the concept
Not necessarily "Express" Related, but what about WinMX
SandieM
Quite the opposite. I couldn't be more excited about VS2005 and the direction that VB is going.
There are a couple of things I'd change as nothing is perfect.
But I do anticipate more expansion in functionality in the future.
Ruba81
I wasn't calling it VB.NET, I was referring to the underlying foundations, since VB2005 requires .NET 2.
Is your implication that I am doing all this for nothing
Miguel Gzz
I agree with Renee.
However, you do have a common concern: when will it end ! The answer is that it won't. just as any with any technology, it will keep advancing. But that doesn't mean that what we learn today will not be valid tomorrow.
It's true, there was a big leap (fotr VB programmers) to go from VB6 to .NET, but things have been pretty incremental from there. The framework is designed to be platform independent (regardless as to whether it will be or not - that's beside the point). As such, it is designed to isolate the programmer from all the lower level hacking, and allow them to concentrate on providing a usable and reliable solution.
WinFX (as I see it) is a replacement for the WindowsAPI - which is very antiquated, now. Of course, it's much more than that. However, it will integrate smoothly with the current .NET framework (managed code). This means it is language independent (some drive Chevys, som drive Hondas: but they all drive on the road). Is it something new to learn Yes: possibly. I'm sure you can (will be able to) program the .NET framework without knowing a thing about WinFX (I could be wrong, but I'm not going to worry about it now - I'm providing solutions for today, not next year). I see WinFX as making life easier for us (developers) to provide solutions: istead of spending weeks creating 'Flying Logos', we will be able to set the FlyingLogo bit to True, and get on with providing real content
.
Don't paralyze yourself over it: there are plenty of Win98, WinNT, Win2000 computers still running - the transition to Vista and WinFX won't be an overnight thing.
dmatalus
First of all, it's not VB.NET anymore it's just VB8 or VB2005.
I think Microsoft is laying down a very solid foundation so that obsolescense will be OS related calls but not the structure of the language itself.
On the other hand, I've seen previews of the functionality of the next version of Basic and if you think that is at all abstract....... you haven't seen anything yet....
Stay tuned......