Hello all
Situation:
We are using Team Foundation Server to manage our developments.
We have a .net application which installs a service and depends on built assemblys which are locate for example under C:\workspace\TeamProject\Main\Solution\bin\
The .aip is located under C:\workspace\Main\Solution\Setup\setup.aip
the other Projects in this solution are located similarly: C:\workspace\Main\Solution\Project\
In Files, Folders and Shortcuts, I have a folder under the Application Folder which is named "bin" and contains a synchronized Folder named "bin", which is installed into the parent and is synchronized with C:\workspace\Main\Solution\bin\ (..\bin)
Unfortunately, TFS Build Service builds the output into a completely other folder:
For example: the build agent checks out the source code into D:\BuildWorkDir\2\TeamProject\Main.Product\Sources\Main\Solution\
The Output Folder would be D:\BuildWorkDir\2\TeamProject\Main.Product\Binaries
in relative notation, this would be not "..\bin" as on local build, it would be "..\..\..\..\Binaries"
So: How to overcome this dynamic thing in Advanced installer?
(I can get a variable out of VisualStudio to do a build in CommandLine)
Best Regards
Jimmy
FOLLOW US
Get the latest news in Application Packaging