>>VB .NET has more differences than just language over C#. There are things like IDE features, IntelliSense benefits over C#, etc. When VB .NET is compared to C#, it is not just the language that needs to be compared but the IDE.
>
>Maybe you should clarify that. Aside from some very minor Intellisense differences there's no difference in the how the IDE behaves with VB now between VB and any other .NET language. What are you talking about? If you are talking about future developments maybe you want to expand?
>
>> While they are both in the VS .NET shell, there are differences. C# is more geared towards code jocking C++ type developers, while VB .NET is more for RAD development. The .NET Framework is not the only features that will evolve. VB .NET will be the best RAD development tool for .NET development, as Alan Griver said in that video clip I showed of him in the keynote at EssentialFox.
>
>That's MS marketing bullshit - I take that from YAG as from any other MS sales person. I repeat my claim that if MS is going down that road they're only inviting competition between the various languages which is self-defeating given the open architecture of .NET to implement an 'equal terms' feature base via the framework. Comptetion between languages is a bad thing and this type of shit is promoting it in a big way. I've seen this already at various other conferences and this is bad news especially given the MS marketing message that all languages get even billing in .NET.

>
>VB developers are a fickle bunch much like VFP developers who live with inferiority complex and MS is trying to desparately fix the flack they've gottne from .NET and C# envy. Knee jerk reactions are hardly an adequate response at this early time in the .NET product cylce...
>
>> AS for your migrating question, that is simply not the case. Myself nor Microsoft as a company is trying to move or migrate VFP developers to .NET. Toledo is being developed and we expect most VFP developers to upgrade when it is released. Many VFP developers are either learning or plannig on using .NET either soon or eventually and I'm simply addressing those developers, it has nothing to do with VFP. Ideally VFP developers get MSDN Subscriptions and giving them VFP, VS6, VS .NET, many versions of Windows, and much more. I hope this clarifies thing here.
>
>Maybe so, but I don't see what the point is for a non .NET product to push .NET as you are at the moment. While I would advise any VFP developer to take a close look at .NET I don't see why the VFP team should waste any of its limted resources on pushing another platform and worse yet migration to it. If people consider the move to .NET there are plenty of resources out there to look into. There's no reason to have it rammed down your throat from the 'inside'.

--------

Perhaps this would be a great opportunity for VFP to pick up the thousands of VB6 developers that don't have the need or desire the learn .NET. As I recall the transistion from Fox 2.X to VFP was partially responsible for a large number of former Fox developers to move on or give up on VFP. The transition from VB6 to VFP has to be shorter than moving to VB.NET especially since it is once again not backward compatible.

A lot of small firms just need simple file processing or an interface to support a few users. In that situation it really is hard to justify all the investment in .NET to gain what?

If it makes sense for VFP developers to consider VB.NET, then it has got to make sense for VB6 developers that don't need the extra power and associated overhead to move to VFP - right?

Is this part of the "best is yet to come" message for VFP? The fact that we could potentially convert thousands of VB6 developers to VFP. Now that sounds like a campaign that could really improve VFP visibility while providing a solid upgrade path to the masses. After all, there are 225 functions in VFP that are not in .NET (and not in VB6?), VB6 developers could begin using inheritance but not have to spend nearly as much time and money to move to .NET. Another plus is that VFP is backward compatabile all the way back to its roots as FoxBASE+. Can't say that about VB.

The new migration path from VB6 to VFP7 campaign sounds great. What an opportunity to expand the VFP marketshare. Hey, looks like "the best is yet to come"...:>)