Jim,

>I've read enough to be able to say that .NET is a far far bigger investment in time, learning, practise, etc. than just switching programming languages.<

OK ... *now* I see your point, and I agree whole-heartedly! Man, what a learning curve!!! But, it's been fun (and frustrating). Definitely not simply a switch to another programming language!!

~~Bonnie




>Right.
>
>My concern was more along the lines that the questioner's employer might be under the impression that .NET is 'just another programming language' like VFP. At least the thread title AND question strongly suggested that to me.
>
>I'm not at all qualified to answer the question posed but do feel that I've read enough to be able to say that .NET is a far far bigger investment in time, learning, practise, etc. than just switching programming languages.
>
>cheers
>
>
>>Jim,
>>
>>>>Wouldn't the answer be more along the lines of 'these are apples and oranges'?<
>>
>>Perhaps ... but she *did* ask about .NET in general, not about C# or VB.NET and so I compared the whole nine yards. And you really can't write a .NET app with just C# and not the rest of the .NET framework now can you? < g >
>>
>>~~Bonnie
>>
>>
>>
>>>Bonnie,
>>>
>>>Knowing little about .NET and having NO .NET stuff in my systems, this is just from the bits I've read...
>>>
>>>Wouldn't the answer be more along the lines of 'these are apples and oranges'?
>>>After all, VFP is "just" a programming language, though a very capable one that is great with data and can exploit most of Windows' functionality including .NET facilities.
>>>
>>>.NET, on the other hand, is a massive collection of things including a framework, several programming languages and several other objects along with a specialized development environment.
>>>
>>>ASSUMING that the question is asked in the context of a "programming language", then there really is no comparison, is there? I mean, to successfully exploit .NET doesn't one have to become familiar with a brand new set of all of the things I mentioned above, the 'programming language' part being but a small portion of it all?
>>>
>>>cheers
>>>
>>>
>>>>Isabel,
>>>>
>>>>Deploying distributed applications is easier in .NET than in VFP, but it is still do-able in VFP. In .NET your application components (.DLLs in .NET's case) can be automatically updated from the server to a remote workstation with no additional coding. While this can be done in VFP as well, you will need to specifically code for it.
>>>>
>>>>Also, for web pages, ASP.NET is pretty cool.
>>>>
>>>>Other than that (though I may have missed a few), VFP can still do just about all you need. < s >
>>>>
>>>>~~Bonnie
>>>>
>>>>
>>>>>My employer asked me What does .NET offer that I can't do in VFP and I'm not sure what the answer is. Does anybody have an answer to this? I really want to get a good listing to talk with my boss.
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Isabel