>As far as frameworks are concerned, I definitely think you will see them. Given that .NET itself is an OO framework, it is a valid conclusion to make that people will subclass as needed to build application components that suit specific needs. To compare this sitation to the lack of VB frameworks in the past is like comparing apples and oranges. First, .NET is fully OO - and that makes a big difference. Second, there is full language framework independence in .NET. Not only will you be able to build frameworks, they can be used and subclassed with any .NET langauge. Further, your components - at least the middle tier ones - can be used in COM-based apps via COM/Interop. IMO, I don't think it is too early. Rather, I think nobody has undertaken the task - or at the very least, nobody *you know of* has undertaken the task.
>

Hi John,

I think VFP framework vendors have a real opportunity here (albeit for a limited time), due to the maturity of their framework designs and the lack of VB counterparts. If they were able to keep the framework interfaces fairly consistent, it could also help with moving VFP apps based on the framework to .Net. I don't know if any of this will happen. Given YAG's new position, I wouldn't be surprised to see a CodeBook .Net