New Post: Mapping Issues When running Install Silently from Powershell script

But that is considering that you have Visual Studio available on every environment that you do an install from and run from the same path within each VS environment when calling the MSI which is not practical because you will not want VS installed on production servers. I am actually using Randy Paulo's script. I build the MSI using the BizTalk Development Framework and then I bundle it with the bindings and the PortBindingsMaster,xml into a zip file that can be copied from machine to machine. If you are not running from within the BizTalk path of VS then the DeploymentFrameworkTargetsPath will need to be changed as well as the path to the folder called "\obj\Debug\redist\Deployment\Framework\DeployTools" which is where the XmlPreprocess.exe runs.

DeploymentFrameworkTargetsPath is easy enough to change since it is already a built-in variable that is part of the framework. I just pass it as a variable in the params to the MSI. However, how would I go about changing the path to the Tools folder (\obj\Debug\redist\Deployment\Framework\DeployTools)?
I'd like to do it in such a way as I can pass a variable in the path to the MSI build like I am doing with the DeploymentFrameworkTargetsPath variable and be able to run the build from both within VS without having problems and also do the same if I pass it as an argument.

I have the following in my .btdfproj file and it works fine if I compile or deploy from within VS or from the command line passing DeploymentFrameworkTargetsPath as an argument. I want to be able to do the same thing for the "Tools" folder. How can I can do this and allow the project to be able to compile successfully within VS?
This works

<Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />

I tried creating my own variable like the following and it does not work. How can I do this?
<Import Project="$(PathToXMLPreProcess)XmlPreprocess.exe" />

thanks
Tim