| Key: |
QB-3746
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Won't Fix
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
Robin Shen
|
| Votes: |
1
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
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:
|
|
|
|
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):
|
|
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): |
Show » |
| No work has yet been logged on this issue.
|
|
Able to use specified version of tools when calling MSBuild and NuGet
