Thanks Craig.

Yes, the V1.0 is certainly daunting, it would certainly not be a wise move until it's matured abit.

Kev
>.Net is an initiative from MS, not a product. It basically uses software as services and XML as the way to pass data and messages between the services. .Net includes servers, SQL Servers, Visual Studio and other products. It is not internet specific. For example, VS .Net can develop Win32 forms to run on desktop machines in a corporate environment.
>
>So, where does that leave VFP? COM components can be utilized with .Net via interop services. We can create both web services servers and consumers. The Fox community has said it does not want to participate in the Common Language Runtime (CLR). IMO, if this meant the death of Fox, the Fox team would have not asked us what we want and would have just made VFP CLR compatable. There are now more members on the Fox team than a year ago.
>
>One other point. VB, C#, the CLR, and other components of Visual Studio .Net are version 1.0.
>
>
>>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