Downloads

FUnit is a NUnit like utility for Unit Testing FoxPro applications. The developer write the test cases in the method that will be tested. The FUnit utility scans the application object modal searching for the test cases. Once found, they are extracted and executed. In addition, Code Coverage can be done as the tests are being executed. Therefore you can see what lines are being tested.

View the entire documentation on line at the FUnit - Unit Testing page.

The purpose of LifeCycle - Build Phase utility is to provide a central application to automated as much of the built process as possible without have to clone code, or replicate the procedure for different projects. It also provides the means to schedule automated builds for daily builds.

Overview

During any development cycle there is point when a project needs to be built into executables. There are different kinds of builds that can take place; the standard build done by the developer to build a local copy of the executables, the Debug or Test Build for the Testers, the Production Build to be distributed to the customers, and possibly many more other types between these builds. The purpose of LifeCycle – Build Phase utility is to provide a single place where all these different types of building processes can be created, maintained, and executed.

LifeCycle - Build Phase utility allows the developer and/or build manager to automate if not all, then most, of the tasks involved in building the pieces to run-time applications. The utility provides a list of all the projects in the overall project, and displays them in hierarchical listing based on dependency. But the main feature of the utility is the Build Styles. Each style is related to a list of Task steps, called the Build Script. The Scripts are performed during the build’s run process. Each of these tasks is a separate entity, which can be either added or removed from the build script at design-time. The build script tasks are creating as standard VFP Class Methods. No special PEM are required to identify the method as a build task, just a few extra comment line are required.

The LifeCycle – Build Phase Light version has a few limitations over the registered Professional version. But these limitation can be removed when the user purchase the Authentication Code that transforms the Light version into the full feature Professional version.

Click here to read more detailed information about LifeCycle – Build Phase.

Installation Instructions

1. Download the self-extracting ZIP file called lcBuild.exe from GLR software web site.
2. Execute the self-extracting ZIP file.
3. Accept all default settings.
4. Open any version of Visual FoxPro of version 6.0 or greater.
5. Change directory to C:\LifeCycle.
6. Perform "DO Demo"
7. When the Authentication Code dialog appears, click the "Skip" button.
8. Then you are in.

Versions

This is the finished release version of the LifeCycle - Build Phase utility version 1.0. If you downloaded the previous Beta version, please delete it before installing this version. Many features and construction of the utility has changed since the Beta release.

Build History

1.01.01 : (08/26/2005) : Build 544

• Slight refactoring of code to enhance startup speed and performance.
• Minor bug fixes.

• Loads and runs in VFP 6.0 correctly without C0000005 error.
• Correctly assigns valid value to MousePointer properties.
• Other minor adjustments.

Please send any comments, suggestion, or bug issues to LifeCycle@GLRsoftware.com

This class encapsulates many of the VFP functions (SYS(), SET(), HOME(), etc) and several windows API and WMI procedures into a single set of classes. Thsi allows for easier access to these functions and increases the readability of the code.

This class is a updated release of the class called "Encapsulates the SYS() and SET() function as methods." I am releasing this version as aseperate download do to fact that I reaganged the methods into logical grouping, for better readability and access.

What's New in 2.0

More ways to generate the unique user code

• Hard Drive Volume Number
• Motherboard Serial Number
• User and Machine name
• Current Domain Name
• Company Name
• Logged On Server name
• User name only
• Computer name
• Network Card Number

12/19/2005
Included NameValue.prg in the zip file.

06/09/2006
Included missing files from the West Wind XMl class.

12/15/2005

Included classes that encapsulate the SysMetric(), FontMetric(), Home(), and OS() functions as named methods.

Have your clients ever ask to have their forms remember their position and size? This neat little control does just that. Now works with VFP 9.0 Anchors. Just drop it on any form, and it will remember its position and shape. The properties are saved in the registry for each user that can log on to the workstation. Now the settings can be either stored in the registry, a network table, or the local FoxUser resource file.

1.52 - fixed mis-spelled variable name - thanks Harry Nunn.

Loads multiple ProjectHooks into a single project manager, and maintain each as seperate classes and class libraries. This is great for when you have separate project hook classes, and like to use them all, but do not want to spend the time combining them into a single project hook. This zip file contents the pHook projecthook, plus all the projecthook in the following list. The demo project uses some of the project hooks as examples.

New to version 1.50
Add the Project Hook Manager form.
    -   Add new Project Hooks to the list.
    -   Remove Project Hooks from the list.
    -   Disable project hooks in the list.
    -   Help screen.
New project hooks:
    -   Switch to Project Orientated TaskList table.
    -   Strip printer info from Report forms.

New to vers 1.51
pHook.vcx
- Fixed QueryNewFile.
- Recurs the Activate and Deactivate events.
- Consolidate common code.
- Add Version property
phTaskList.vcx
- Switch Tasklist when more then one PM open.
ph_Manager.scx
- minor fixes.
- Regenerate PHL file only when something changes.

The following is a list of Project Hooks I have found while looking around the web. If you like to contribute your project hook, email it to Work@GLRsoftware.com. Include your name and email address, plus a short description of the purpose of the project hook.

Thank you, Greg.

Version 2.11

Yes, it's back.. But a new and improved version. Faster, Cleaner, and Extendable. I took a little time and rewrote the entire routine to allow the developers to add their own data drivers and cleaned up the code so I can better manage it (the first version became unmanagable.)

Query is a single function that allow you to manipulate various types of lists of data sources (Collections, Arrays, Cursor, XML data, delimitered strings, and etc) with the standard SQL statements.

Use a standard SQL statement to filter, sort, combine data sources, and then convert to a different data source. Also, with the Update, Insert, and Delete SQL statement, you can manage the lists as if they were cursors.

If you are interested in see this in action, you can download a copy here and run the Demo.prg program.

Array Class Library Collection CSV Cursor Database Drive Driver Environment Event Log External

Field File FileUser FTP Graphic IndexTag INI Keyword ListBox Locale NetResource

ODBC Path PEM Prg Printer Process Registry Screen Service Stack

String Table Task UserGroups Users Variable XML

I am looking for any drivers you may have developed for the Query tool. If you have one or more or even an idea for one, please contact me at Query@GLRsoftware.com. Thank you. Greg