dziubanmaciej

Huh, that's sad, but concrete :) Thanks for the answer.

Sorry, but I would rather hear an explicit "Not a feature, not gonna do it", than receive nonsense arguments about non-default installation path not being supported and then get ghosted.

Hello? Please answer my questions.

Ok, that's concerning. Where is it documented? Why do you give your users an option to select installation path via GUI, if it doesn't work correctly? There is no warning in the installer. Why won't everything work with changed installation path? I find it hard to believe for such an advanced software. Most of programs just store installation path under some registry key and use it from there instead of hardcoding Program Files (x86) location. Let'

Umm, I don't think so, GUI installer (graphical installer, where you click) does offer a choice of installation directory. I'm asking the same for CLI (command line installer, where you only type commands).

Hey, I'm using Chocolatey package manager to install all of my software. I normally pass additional command line arguments like /D, /DIR or /TARGETDIR (depending on what a given installer expects) to select installation directory. How to do it with Fences 3? The installer looks like it's an MSI installer embedded in .exe file, so TARGETDIR="D:\My\Installation\Path" should work but it gets installed to the default Program Files (x86) location. <p