I am pleased to announce on behalf of the authors of “Hacker’s Guide to Visual FoxPro” (Tamar Granor, Ted Roche, Della Martin, and me, with contributions from Steven Black) that the book is now open source: https://hackfox.github.io/.
Most people consider HackFox to be the “bible” for VFP developers because it goes far beyond the VFP help and tells you how VFP really works. It advises which commands and functions to use, which to avoid, and the best way to accomplish certain tasks.
HackFox has gotten a little long in the tooth since it wasn’t updated after VFP 7. Hopefully making it open source will allow it to flourish as people in our community update existing topics and add new topics for VFP 8 and 9. Also, the online content currently closely matches that of the book but that may change over time so it can become a better online resource.
Inspired by Steve Black open sourcing INTL, I’ve decided to open source Stonefield Database Toolkit (SDT).
SDT was originally created in 1995 and Stonefield Software sold a ton of copies of it over the years, making it one of the most popular add-ons for Visual FoxPro ever. However, nearly 25 years later, my baby has grown up and it’s time to open it up and share it freely with the VFP community that has supported us all this time.
You can find the open source version of SDT at https://github.com/DougHennig/StonefieldDatabaseToolkit. It includes all source code, documentation (as a CHM file, including West Wind HTML Help Builder source; I didn’t convert it to Markdown), and tutorial files. Enjoy!
When a customer reports a bug, we usually fix it immediately and send them a “hot fix”, which is usually just an updated EXE. Because it doesn’t go through our usual build process, the EXE isn’t digitally signed, which can cause issues on some machines. I created a batch file to sign the EXE but most of the time forget to run it before sending the EXE to the customer. Then it occurred to me I could automate that process using Project Explorer.
I created the following program and added it to the Addins subdirectory of the folder where Project Explorer exists:
lparameters toParameter1, ;
tuParameter2, ;
tuParameter3
local laStack[1], ;
lnRows, ;
lnI, ;
lcApp, ;
lcDescription, ;
lcCommand, ;
lcFolder, ;
loAppRun
* If this is a registration call, tell the addin manager which method we're
* an addin for.
if pcount() = 1
toParameter1.Method = 'AfterBuildProject'
toParameter1.Active = .T.
toParameter1.Name = 'Sign EXE after building'
return
endif
* This is an addin call, so if we built an EXE, sign it.
if tuParameter2 = 3
lnRows = astackinfo(laStack)
for lnI = 1 to lnRows
if 'projectexplorerui.vct' $ laStack[lnI, 2]
lcApp = fullpath('..\projectexplorer.app', laStack[lnI, 2])
endif 'projectexplorerui.vct' $ laStack[lnI, 2]
next lnI
lcDescription = inputbox('Description', 'Description for EXE')
text to lcCommand textmerge noshow pretext 1 + 2
"SignToolPath\signtool.exe" sign /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /f CertificatePath /d "<<lcDescription>>" /p Password "<<tuParameter3>>"
endtext
lcFolder = justpath(tuParameter3)
loAppRun = newobject('APIAppRun', 'APIAppRun.PRG', lcApp, lcCommand, ;
lcFolder, 'HID')
loAppRun.LaunchAppAndWait()
endif tuParameter2 = 3
return .T.
Substitute SignToolPath with the path to SignTool.exe, CertificatePath with the path and name of the certificate file, and Password with the password.
This program is a Project Explorer addin that’s called after a project is built successfully. This code checks whether it was an EXE (we’re not going to sign an APP) and if so, finds the location of Project Explorer so it can use the built-in APIAppRun class to call SignTool.exe to digitally sign the EXE.
Now, whenever I build an EXE in Project Explorer, it’s automatically signed so I don’t have to remember to do it.
If you missed Southwest Fox 2019, you missed a seriously great time. Check out the hundreds of photos (Facebook and Google Photos) our Social Media Manager Jody Meyer took and watch the Keynote presentation by Kevin Ragsdale on YouTube: Part 1, Part 2, and Part 3.
Congratulations to the 2019 VFPX Administrators Award winner Christof Wollenhaupt for his FoxMock project. Congratulations to the 2018 Speaker Award winner Tuvia Vinitsky.
We announced dates for next year's conference already, and it’s a little later than our usual October dates: November 12 - 15, 2020. I hope to see you in Phoenix next year!
Posts
All Comments
