History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3746
Type: New Feature New Feature
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Robin Shen
Reporter: Robin Shen
Votes: 1
Watchers: 0

If you were logged in you would be able to see more operations.

Able to use specified version of tools when calling MSBuild and NuGet

Created: 18/Jun/21 12:13 AM   Updated: 23/Dec/23 01:04 AM
Component/s: None
Affects Version/s: 11.0.3
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: None
Image Attachments:

1. image.png
(142 kb)

 Description  « Hide
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):

 All   Comments   Work Log   Change History      Sort Order:
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.