I set up some pre- and post-Build Events for a number of my targets, to trigger associated Powershell scripts. It all worked fine on my side, but for another colleague sharing the project, the events never triggered.
Exhaustive research determined that it was because her projects were stored in a folder structure that contained spaces in the folder names (e.g. \My Projects\), and this caused all uses of the $(ProjectDirectory) Build Variable to fail.
Is there any way around this?
Build Variables and whitespaces
-
Feebeegeebee
- Sr. Propeller Head
- Posts: 213
- Joined: Wed Aug 08, 2012 8:38 am
- Location: UK
Re: Build Variables and whitespaces
I simply wouldn't recommend using a directory structure that contains spaces at all. Windows might cope with it, but other platforms don't.richt wrote:Is there any way around this?
I learnt this long ago, when inadvertently checking a new help output into our (Linux-based) source control, ready to be included in s/w builds. It broke the builds and delayed them from going out - just because one file or directory in my structure had a space in it... Never made that mistake again!
Feebeegeebee
-----------------------------------------------------
Using Flare 2022 on Windows 11 (64-bit)
-----------------------------------------------------
Using Flare 2022 on Windows 11 (64-bit)
-----------------------------------------------------