Does Microsoft Visual Fox. Pro 9 run on Windows 1. I’m sure many die- hard Fox. Pro developers are curious if Visual Fox. Pro 9. 0 SP 2 will install and run on Windows 1. Well, I wanted to be one of the first to find out, just like I did back when Windows 8 was first released in its early preview. So, let’s find out…First, I installed Windows 1. Preview (6. 4 bit) in a Boot. Camp partition on my 1. Mac. Book Pro. (Don’t worry about this Mac stuff, it’s still just Windows running on live hardware, just like if it were a Dell or HP computer). That went very smoothly, and I did a full install, blowing away the Windows 8 playground I had been using that partition, instead of updating it from Windows 8 to Windows 1.
Anatomy of a Form. Nearly every application or user utility that you write in Visual FoxPro will include at least one form (and probably quite a few). Tool to export, import, migrate and convert data between different databases and delimited flat text files. Next, I gently inserted the Visual Fox. Pro 9 CD that I still have from circa 2. First, it prompted me to install some “Prerequisites”, which it did with no problems. Next I moved on to the main VFP install, and I took all the defaults, then the CD spun around for a bit, and finally, it gave me a nice message screen stating “Setup is complete” and “There were no errors during setup.” Looking good so far!! Next, I downloaded and installed Service Pack 2 for VFP 9, and once again, got this nice little affirming message box: Finally, I “installed” the VFP 9 Hotfix 3 for SP2 (i. We now have a promising Microsoft Visual Fox. Pro 9. 0 entry in the fancy new Windows 1. Start menu: Yes, but does it actually run?? Now, I finally get to find out if we can run the fully patched Microsoft Visual Fox. Pro 9. 0 SP2 Version 0. Windows 1. 0. So, I launch it from the Start menu, and quickly go the Help –> About screen: One small issue with Task Pane…If you launch VFP 9 it will initially show the the Task Pane, but you will get a small error in the view area of the Task Pane window. Don’t worry, I’ll show you how to fix this below.)Class definition MSXML2. DOMDOCUMENT. 4. 0 is not found. The issue is that Task Pane requires MSXML 4. Core Services. If it’s not already installed on your Windows 1. Task Pane app from the VFP IDE. However, this problem is easily fixed… You need to download the MSXML 4. Core package from: http: //www. Family. ID=3. 14. Display. Lang=en#filelist. Once, installed, now Task Pane will work properly: Now, let’s run some code…Okay, it says the right version number all, but we need run some Fox. Pro code to make sure this thing actually works… So, I just downloaded the Thor Tool Manager for Fox. Pro from vfpx. codeplex. Thor. app to put VFP 9 on Windows 1. Thor uses tons of well- architected Fox. Pro code to do it’s magic, along with some UI forms, and it makes use of our beloved Fox. Pro cursors, so I figured this would be a good test. I selected about 1. VFPx tools from the Check For Updates form in Thor, and it nicely proceeded to download and install all the tools, and gave this confirming output for each one on the VFP desktop as it did its work: I think we’re good folks! Next, I ran a few of these tools, just to make sure they’d fire off, and they did. I’m pretty certain at this point, that my business apps would work just fine here, if I took the time to finish out this developer setup. So, I haven’t done any real coding work in the IDE, and I probably won’t any time soon, but from my basic tests in this experiment, it sure appears to me that our old friend Visual Fox. Pro is ready to continue its legacy of being an awesome development tool, even on Windows 1. Windows 2. 0 and Windows 3. Finally, here’s a peak at the whole IDE running in Windows 1. You can see I docked some windows, and you can see the shading effect that Windows 1. Microsoft Visual C++ 2. Redistributable - Free download and software reviews. Pros. Retains the outstanding features from VC6 and VC2. Great debugger, good interface. Cons. Cannot write a program under MSCV 2. Summary. I am used to writing a simple program and being able to copy it to a customer's computer and execute it. You can't do that anymore. Copying the EXE and DLLs to the target directory doesn't work anymore The problem has to do with DLLs. You get programs expecting different versions of DLLs, so Microsoft did something about it. All DLLs have been moved to the Windows\Sx. S directory and given names decorated with arbitrary strings. OK, I can live with figuring out how to build an install project, running it, and then installing the package on the target computer. Problem is, that's not enough. Once you do the installation and try to execute the program you get an obscure error message about initialization failing. It suggests that you reinstall the program, but of course that doesn't help. There are three work- arounds. Install the VC run- time on the target computer. The run- time is free, but it is a 9. M download and takes a while to install. People who never program should not need a compiler on their computer. Use static linking of the run- time libraries, which will blow up your program size. Use MSVC 2. 00. 5. The third solution is the most elegant. The 2. 00. 8 version of Visual Studio has added some new goodies on the Tools and Test tabs, which I never use. It is set up to allow access to the web and databases. I don't use any of that either, since I write scientific programs for use in- house. Before installing VC 2. Reply to this review. Was this review helpful?(0) (0).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |