Hello,
Thank you very much for the detailed test-case and for the sample project.
I have done some tests and this looks like a misconfiguration on your side.
Basically, based on the
CONFIGPATH property, you create a folder in the
"Files and Folders" page (a property based folder).
Now, in your PowerShell script, you set that property to " ", which obviously is not a valid path. During the
"Paths Resolution" action group, a validation of all the folders from your project is done and that error appears if a path is not valid.
The name of the action is
"CostFinalize".
CostFinalize ends the disk space costing and resolves the folders in the project
Now, if you change the value of the CONFIGPATH property in your script from " " to "", the following happens:
- the "" value basically means an empty property. A property can have two states:
1. it has a value and therefore it exists
2. it does not have a value and therefore it does not exist
In your case, if you set the property to "", this is what happens (taken from the log file):
MSI (c) (D8!F4) [13:23:05:407]: PROPERTY CHANGE: Deleting CONFIGPATH property. Its current value is ' '.
and then:
MSI (c) (D8:30) [13:23:05:422]: PROPERTY CHANGE: Adding CONFIGPATH property. Its value is 'C:\CONFIGPATH\'.
Since no value is given to it.
With that being said, please give a correct value (a valid path) for the
CONFIGPATH property and this should work as expected.
Best regards,
Catalin