In My Opinion.. It looks like the .net is a advertising wrapper arround, three development products which MS is promoting
VB C# and C++ (not to mention its use of MS Sql) as the server / or data pump.

In its core, there are a few things which make the .net attractive.
1 the UR , which allow all app, written in to it(those three right now) to share a command runtime. (reminds me of the promise of java.)
2 VB and C++ are finally being fully updated to handle OOP language syntax.
3 C# a new language - sort of a C like / java like language, which will be the building blocks - or can make the building blocks for the .net.
4 its seems to be written arround the concept of Application services, where one app could get data or calculations from another app, over the internet. Ideas like embeded ups tracking information, Embedded patient history lookups , data migration from one platform to another. But... MS has to first build it, then get developers behind the idea, and start to understan and write to it. Its going to be a few years out until we really see it working in production.


The .net holds promise for the largest enterprise application builders, like siebel, where they already use VB / c++ to develop applications. They way I look at it, is it will be, the way that MS works out how to move to the enterprise level applications.. Some exist now, and MS is looking to get a larger share of that market the .net is how they intend to attack it.

Not a bad idea/ actually, many of the other enterprise level apps I have seen recently are still running on leagcy code, or terminal screens, which business people are quiet frankly tired of, an wanting to push to the level of what they come to expect with Outlook and excel.


Where does that leave the FOX ?

JUST MY opinion, but in about the same place it wasa before Bill though up the .net soltuion. No better no worse.

Fox, will have I assume most of the best MS gui controls, in time, or before the VB /C++ world will see them. It has a easy way to get to SQL data, and has maintained a solid following for small to mid sized companies for years. Fox an its heritage has never really been thought of as part of any other package. but could stand alone, or be part of larger solution. Its beauty is in its nitche. What cant be done with FOX? Where is the brick wall.? its just not there.

in my 14 years working as an in house developer, (working for three different companies) they could never care less what development platform I was working in, just as long as I could get to data, comsume it, spit it back out / first in paper then fax, then email and now publish results on the web. It just doesnt matter, What platform is used. Results / and speed and acuracy . Thats what fox has always allowed me to do. How Ken , and the rest of the MS team choose to market this unique ability to for Fox,to be the go between, and be the one be all end all data comsumer. who knows. But I dont worry about the .net. and not all that concerned that Fox is not in it. the Fox will survive nicley with or without it.
Bob Lee

>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