Tuesday, February 14, 2017
But moreso, the open-source VFPX is more than 10 years old (I believe the official birthday would have been around June , 2016). Nowadays Microsoft is open-sourcing more of its underlying code. I'd like to think that if they had this attitude 10 years ago, VFP would have been open-sourced but that's doubtful. The proprietary VFP engine and concepts have made its way into countless Microsoft products.
I always think about open-source projects as a bit of leap-of-faith. That's because open-source projects aren't always like the public domain projects of yore. By their very nature, they rely on a group of people providing feedback and pushing forward from a version 0.1 all the way to full release cycles. That's not just open-source, of course - Microsoft is notorious for starting projects and then abandoning , sorry, folding them into newer technologies. I came across an older project of mine that used DDE, it made me think fondly of building interactive spreadsheets with Windows 2.0.
But even though Visual FoxPro is a defunct product from Microsoft, the VFPX project is still going strong with over 14 updated projects in the past year. These projects keep FoxPro applications able to use popular products and technologies.
One of the best things is that many of them provide these functionalities without relying on special DLLs or COM automation. Need to go beyond VFP's limited Excel output? consider the XLSXWorkbook project. Doing payment systems? Look at Stripe integration.
The great thing about VFPX is that many of the older projects are still getting updated or do their job exactly as they need to and aren't obsolete.
VFP and the FoxPro community has always been one of "if you need it and it's not there, build it and then share it". That attitude continues to this day.
Monday, August 22, 2016
Doug made a great point about how in this age of Google where you can find a quick answer moments away, the real value of conferences is the ability to deep dive into a subject and speak with experts and other developers. StackOverflow may rock for finding those answers but it certainly helps to listen to something longer than a 10 minute answer about issues that you may be having.
The conference is coming up quickly - September 22nd-25th and there are both pre and post conferences and other vendor training sessions. Rick Strahl is bringing his West-wind Web Connection training to the show and Tuva Vinistky is offering a FoxInCloud post-conference as well.
Friday, January 29, 2016
In this job, we're working for the main Development group who provides services to internal clients. Recently we showed these internal clients how we were doing full sanity tests prior to each iteration being marked as Complete (we do a three week iteration - more on that in a future post). When we showed the client the Test Cases and the steps, the client immediately wanted them. They were hiring new testers for their own testing and were worried about the time it would take to get them up to speed.
Note: while we've been using the automated tests, there are some aspects of the software that aren't supported under CUIT. In addition, test cases with steps help junior testers become more familiar with the actual application.
Short Answer: Use the Export approach
At first, I figured I would use SSRS to build a useful report. However, there is no easy way to get to the data. The post here suggested the following SQL:
declare @fldIdSteps int = (Select top 1 fldid from Fields where ReferenceName = 'Microsoft.VSTS.TCM.Steps')
where FldID = @fldIdSteps and id=6514
This works except that you then see that the actual steps are stored as XML.
Then I come upon this link. While Microsoft is certainly pushing people to use VS Online to get the most current features, I was happy to see that this was also available in TFS 2013 Online.
1. Find your Test Suite.
2. Switch to Grid Layout.
3. Now you can cut and paste it into Excel for nicer formatting.
But there is a better way - THIS one.
Just right-click on the Test Suite and Export for Email.
I then took the email and cleaned it up in Excel. Fast and easy and now the client is super happy!
Wednesday, November 11, 2015
String.Format for Visual FoxPro
[Originally Published in FoxRockX, September 2010]----
Shared via my feedly reader
Wednesday, August 05, 2015
Sunday, July 19, 2015
I was surprised that Wakanda wasn't listed - but it seems to be far more than just a framework, more of a full blown application tool and stack.
And then I saw this great graphic which captures it to a T
Wednesday, June 17, 2015
Now, whenever I need to search for code within files, I can do it all in Visual Studio, even if the project isn't loaded.
Friday, September 26, 2014
- Not having time to deal with your review backlog.
- Delaying a release because your reviews aren't done yet.
- Posting reviews that are no longer relevant since the code has changed so much in the meantime.
- Doing poor reviews since you have to rush through them at the last minute.
Wednesday, September 10, 2014
Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.
Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"
Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.
Guess that means the iPhone 8 will be back to boxy.
And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming. The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" worthy? No. Maybe I'm just jaded.
One more "bad thing" is that the Apple Watch (which does look very cool) requires an iPhone. So now you can walk around with more Apple devices instead of just one. If you're going to change my life, make my load lighter, not heavier.
So much for real Continuity.
Thursday, August 21, 2014
At a client recently, we developed our WPF application under Windows 7, tested it under Windows XP and everything looked great.
Then it was deployed.
As it turns out, one of the deployments was over a Citrix server that forced applications to run under Classic mode.
Those of you who have worked with various operating systems over the years will know what I'm talking about. Classic mode isn't quite classic, unless you are one of the few who think playing bar pong on an 84" TV is superior to playing one of the more dimensional games. Or maybe one of the few who like to get up and change the TV channel rather than finding the remote. Or one of the .... (you get the idea)
While most things converted well, Tabs do not. In WPF, we have these beautiful tabs that look fresh but over in Classic mode, they have the look and feel of, well, Classic Windows 95 and VB 6 applications.
The application was demo'd to the client under Windows 7 but deployed under Windows Classic so all of a sudden, the user's experience went from "wow, that looks great" to "what kind of crap did you give me".
But all was not lost. I found this very old (2006) but super useful post about forcing WPF to use a theme. In the end, it was as simple as adding a forced reference to PresentationFramework.Aero in the solution and adding
<ResourceDictionary Source="/PresentationFramework.Aero;component/themes/Aero.NormalColor.xaml" />
to the Resource dictionary (or to the Application.xaml file).
Voila our tabs went from crap to zap!
To make the experience even more sweet, that post from 2006? The blog is still being updated today (a lot more posts than here recently as well). Well done, Aelij Arbel, well done and Thank you!