Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please introduce $(Build.BinariesDirectory) for migration purposes #369

Closed
jessehouwing opened this issue Aug 6, 2015 · 2 comments
Closed

Comments

@jessehouwing
Copy link
Contributor

I understand this is something we might be trying to move away from, but in order to upgrade old XAML builds to the new engine and to even old style TFS2008 builds which depend on redirectinr the Project output, it would be nice if there were a $(Build.BinariesDirectory) which we can substitute.

Right now I’m depending on $(Agent.BuildDirectory)\Binaries and $(AGENT_BUILDDIRECTORY)\Binaries to set these values and then pass them to MsBuild. That way the old packaging scripts, Wix scripts and other things that expect to find a temporary folder in a certain format all “just work”.

I don’t want to use the $(Build.StagingDirectory) for that, as that gets cleared after each build and breaks incremental builds.

I tried defining my own variable $(Build.BinariesDirectory) = $(Agent.BuildDirectory)\Binaries, but it looks like we can’t (yet) create “self-expanding” variables.

@bryanmacfarlane
Copy link
Contributor

We'll discuss. Thanks

@bryanmacfarlane
Copy link
Contributor

This has been checked in. You should see it in the next sprints rollout in a week or two.

See: https://github.com/Microsoft/vso-agent/blob/master/docs/workfolder.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants