The CLR is meant to address some of the shortcomings of MS current offerings. I haven't developed enough Web-enabled apps, especially in a large enterprise environment. But from talking to people who have, and from reading posts from folks like Rick Strahl, there are numerous shortcomings in the current environment.

For folks such as ourselves, particularly ones who use MS tools for a living, these shortcomings are not show stoppers.

However, there are many, many people who do view these shortcomings as showstoppers, and that is why they have turned to Java to do their Web development.

Here is Los Angeles there is a ton of Dotcoms. Yet I don't here of a hugh call for VB, ASP, etc. knowledge. OTOH, Java folks are at a hugh premium here. This has not escaped MS' radar.

PF


>I don't see how one affects the other. Using VFP, COM, n-tier design and a remote backend, you can write an enterprise solution. CLR has nothing to with it (IMO).
>
>>Exactly, which leaves VFP as the small/medium size company platform. It remains to be seen how much resources MS wants to exhaust in this marketplace.
>>
>>PF
>>
>>>Yeah, it might be nice to be able to compile to managed code. But for the amount of effort that it would take the VFP team to do this, only to arrive at a product that works almost exactly like another product that I already own (VB), I say why the hell bother?