>We are in the dilemma of VFP vs. .NET for web apps. My flashy IS guys are pushing for .NET because they don't like the VFP run-time that has to be installed on all workstations running a VFP 6.0 app.
>
>So, the question is: do workstations require a .NET runtime to be installed to run a .NET web app?
>
>thanks
>
>bonnie

With VFP6, you don't need to install the DLLs on all workstations. I have successfully copied the DLLs into the same shared network folder as the executable, and it works fine.

I do prefer to install the DLLs on each workstation, though, and it is not complicated to do it. The main reason I switched to this is because I ended up having executables in several folders, and didn't want to have a copy of the DLLs on each folder on the server which included executables.

The setup program (created with the Setup Wizard) with which I copy the DLLs is also handy for installing additional suport files: support for CHM help, and ActiveX, mainly.

Finally, a triviality like having to copy 4 MB of DLLs to each workstation shouldn't be the main consideration when choosing between VFP and .NET.

IMO, the #1 question, if you want to use .NET, is: are you ready? Because, if you know VFP, and don't know .NET... well, be prepared for some delays.

.NET seems to be quite interesting, and I don't want to discourage you from learning it. Just don't jump to the conclusion that just because it is new technology, everything will work better. If you don't know it well, it won't. So, if you decide to learn .NET, take some time to learn it first. Then, you can gradually switch, if you think .NET has enough advantages.