Closed maxps closed 9 years ago
It needs updating; there's a list of known locations.
PRs accepted btw =)
Am I correct in guessing that these lines are the ones responsible for finding the MSBuild executable? Is there anywhere else that would also need to change?
Yes, you're correct, there are no other lines that find it.
Kind of the same issue here. Using Albacore on my DEV machine and it works. But I'm currently using it from a cmder (http://bliker.github.io/cmder/) console "chrooted" to a Visual Studio command prompt. Looks like everything gets picked up as it should for my (web) project.
Now trying to use my Rakefile on a build server doesn't work. Installed the Microsoft Build Tools 2013 that are now available on the path mentioned above.
Regarding the msbuild discovery. It should be fairly easy to add the "new" path. But is this the always desired msbuild executable then? Or ask differently should there be some kind precedence logic?
By default I imagine the 'latest' would be preferrable, by means of prio in a string array?
I'm trying to compile a Visual Studio 2013 project which requires MSBuild 12, and it looks like Albacore's build task isn't picking up the proper version of MSBuild.
I think this is because the build task doesn't look in the new location for 2013 binaries (C:\Program Files\MSBuild\12.0\Bin), as per the MSDN blog post here.
Am I missing something, or is this a behavior that needs updating?