Dependency on IncludeSSO

[mdoelker]

Hi there,

I ran into issues when using this great script with some applications that did not create an SSO entry, because IncludeSSO was False in Deployment.btdfproj. I discovered that the Deploy script requires this to be True, as it reads out the ProjectPath from SSO which in my case was resolved to null, creating problems when uninstalling backreferences:

Cannot bind argument to parameter 'ProjectPath' because it is null. ---> Microsoft.PowerShell.Commands.WriteErrorException: Undeploying back references failed

Maybe ProjectPath can be read elsewhere to make it independent from the SSO setting, like from an entry in the registry key that is created by this script. It should at least be mentioned that this setting has to be enabled for it to work correctly.

Cheers
Malte

[milkyware]

Hi,

Thanks. I'll make a note of that and update the readme. The reason for using the SSO is this is most likely up to date place for the installation folder. I believe BTDF does store it in the registry as well so I'll take a look

Cam