| << Back to previous view |
|
[QB-3746] Able to use specified version of tools when calling MSBuild and NuGet
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 11.0.3 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| File Attachments: |
image.png
|
| Description |
|
Yeah, I'm working out some of the details on getting the .NET builds functional, but it's immensely painful actually. We have projects spanning versions of Visual Studio from 2012 to 2019, .NET versions from 3.x to 5.x, so using any of the QuickBuild steps right now just isn't cutting it.
Jenkins and TeamCity both provide build steps that allow you to select which installation/version of the Visual Studio tools to use right there in the step configuration. With that information, the build step can figure out where the tools are (I believe everything uses vswhere to locate the tools): |
| Comments |
| Comment by Steve Luo [ 30/Jan/23 03:24 AM ] |
|
Do you hope to specify the path of MSBuild and NuGet in the step? Please click the "Show Advanced" link to open the advanced settings and where you can specify the path of MSBuild and NuGet.
Let me know if this can help. |