Ken,

My feeling is that the Common Language Runtime (CLR) is a strategic move. In distributing applications, I'd like the ability to run them already present on a client's server. It's a perception thing with clients. Our reality may be that it makes no difference. Their reality may be that VFP is out of step.

I'm hoping to hear that Version 8 will be moving toward a CLR compiler. In 2 years we should know if it will take hold. I think it will with the resources MS is devoting to it.

Our shop will be there for the keynote. Looking forward to it.

Pat

>>Hi
>>
>>A few people I know are asking about .NET, and what I mean about that is: Where will .NET come into Development and where does that leave FoxPro.
>>
>>My instant response has always been - "what about it?". VS.NET, as far as I'm concerned has it's place in Web development and FoxPro is still no.1 for DB/Web/Desktop development - so why would we want to go VS.NET?
>>
>>Can I have your comments - ideally can I have a response to give these people who technically know nothing about VS.NET and FoxPro to make them think (IMO) that they've asked a silly question.
>>
>>Or maybe I'm wrong!
>>
>>Thanks
>>Kev
>
>Visual FoxPro 7 is fully compatible with .NET XML Web services by supporting SOAP and WSDL. There are many features in VS.NET that VFP 7.0 developers may find very useful, like a rich XML and XSD editor, ASP.NET for web page creation from data (like VFP data via VFP7 OLEDB provider), and more. I will address this topic at DevCon in more detail and on the http://msdn.microsoft.com/vfoxpro web site after DevCon in even more detail.