hi,
since the bat files for deploy/undeploy... are dropped in favor of shortcuts, which i dearly appreciated at first glance, we had quite the problem to make them work.
all paths are provided full qualified and therefore can potentially be quite long - too long for shortcut arguments which are limited to 260 chars (and the rest is simply cut off without mentioning).
in our environment some properties were not provided to the msbuild call leading to unexpected results.
our workaround was to shorten the argument list by putting some of the needed properties in the msbuild calls in serverexecute.targets file. an ugly solution since we did not want to modify the original files to prevent messing around again and again when updating.
yes we could have used good'ol'bat-files instead but i like the idea of creating shortcuts, so pls look into this and maybe there is a (clean) way to shorten the paths/arguments?
greetings alex
Comments: ** Comment from web user: tfabraham **
since the bat files for deploy/undeploy... are dropped in favor of shortcuts, which i dearly appreciated at first glance, we had quite the problem to make them work.
all paths are provided full qualified and therefore can potentially be quite long - too long for shortcut arguments which are limited to 260 chars (and the rest is simply cut off without mentioning).
in our environment some properties were not provided to the msbuild call leading to unexpected results.
our workaround was to shorten the argument list by putting some of the needed properties in the msbuild calls in serverexecute.targets file. an ugly solution since we did not want to modify the original files to prevent messing around again and again when updating.
yes we could have used good'ol'bat-files instead but i like the idea of creating shortcuts, so pls look into this and maybe there is a (clean) way to shorten the paths/arguments?
greetings alex
Comments: ** Comment from web user: tfabraham **
The ProductID property is available at all times in your .btdfproj, so you could just add a new Target in the .btdfproj that references the ProductID property, and call that target from your custom shortcut. I don't see a need to pass ProductID via the command line in the shortcut.
One comment on the process -- it seems like you have a file locking issue because if MSBuild is launching the uninstall, then by definition the MSBuild targets/btdfproj are in use by MSBuild and can't be removed by Windows Installer.