>>>1) A class in VB / C++ / C# can be subclasses in any other language.
>>>2) Types are now consistent between languages.
>>>3) Error handeling is consistent between all 3
>>>4) ASP+ pages can be compiled and if various languages were used on different pages they would be optimized when hit.
>>
>>Sounds cool, but how practical is it reall? Its nothing more than writing 3 version of a FoxPro app and using different include files so you can use 3 different syntaxes. Eventually, the different syntaxes will become annoying and hard to maintain. If MS really wanted langauges to interact, they woudl have only made one langauge. Selling VB.NET and C# together is really an excuse for them to charge more for one product.
>>
>>Would you like to be maintaining an app where 1 class is written in 3 langauges? Nightmare, yuck.
>>
>>>VFP not getting any of this is poor.
>>
>>Seriously, we need to stop thinking of what our options are in VFP, and start remembering that VFP is part of a suite of tools. They should all have a purpose for being there. With the CLR there isn't one. If VFP was a CLR langauge, what would its purpose in the Suite be? It wouldn't be Middle Tier anymore, because it no longer has the performance gains that it does now. And MS certainly doesn't care about keeping the VFP syntax around as long as it does the VB syntax.
>
>

---

>
>>Would you like to be maintaining an app where 1 class is written in 3 langauges? Nightmare, yuck.
>
>I think you see this in the wrong light Mike. Say the C++ group did an app, and part of it fits into your list of outstanding tasks for a VB thing. You take their commission bizObject and drop it on your form. or you subclass the bizObject and add to it so it fits your need. That is a benefit in my opinion.
>

Does this mean you can sub-class a C# object in VB, and enhance the subclass with VB code?