On 11/20/2017 12:20 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Oh hell no....I haven't deployed to Program Files for YEARS. Many here will tell you that you avoided so many M$ problems by installing in your own app folder off the root (C:\MBSS) instead of following M$'s advice. Chime in all, if you want to give an "amen" for that.
Amen.
The best "architectural" decisions I've made on the Windows platform have been those that have directly contradicted Microsoft "best practice" statements.
Of course, when I mean best decision, I'm evaluating based on ease of deployment, maintenance, upgrade, and error-tracing. Many of my applications have run since Windows 98. Apart from coding to take advantage of newer VFP features, I pretty much never had to spend time fixing the design because of something MS did (although around the time of Vista there was MessageBox() weirdness and "ghost" files...). I compare that to what I've seen in massive rewrites of COM+, Net<something... right after COM+?>, IE (browser-based) code (but browsers were supposed to save us from that???!!! - ROFLMAO) - all because of Windows version changes (or even just IE changes).
But, in agreement with Ted, if I was solely out to just keep a job due to MS-created breakage, my decisions were probably not the best. Hmmm.... I wonder if MS labeled those things as "best practices" because they were best for MS: as in the best way to lock-in development staff on Windows (play on laziness and lack of computer science knowledge), and therefore lock-in the user base. Maybe MS wasn't as stupid as they appeared to be.... Nah.
-Charlie