Regardless of how you'd prefer to classify it or where you think it should be installed, that doesn't justify removing the ability to select a custom installation location - an ability that has existed in Windows software for decades. Fast forward, now we have a very select few of vendors that think users need to be saved from their own selves because they're deemed too stupid to choose their own installation location.
I've never used the quoting functionality here, so I apologize if I goof it up. [quote who="sdRohan" reply="13" id="3826780"] This practice is mostly about ' saving them from themselves '. [/quote] Famous words many times over from those assuming that people need it. [quote] ....the result of it not being in a place (ProgFiles) where the app could do all it needed to or to have Windows treat is properly. [/quote] That kinda m
I do understand - but by and large, Sean, the vast majority of software vendors provide the option for a custom installation location and just via environment variables and the Registry alone, Windows provides great flexibility in supporting this. I don't mean to be offensive, but when I see a vendor do this, it comes across as laziness - something done more for the benefit of the developer vs the customer. That being said, Fences is a great product (as attested by my upgrade purchase of v4 e
As a developer myself, I really do not understand why more software vendors are starting to eliminate the option for a custom installation location. The option to do that has been around since Windows was still in its 3.x versions. Many people like myself prefer to reserve C: drive for the system (OS) only, and install all other apps on a different volume. Taking away this option and forcing users to install a piece of software where the vendor thinks it needs to go feels like a great big mid