-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error when both VS2017 and VS2019 are installed on same server #11
Comments
Seems that one of the cmdlets in certain cases is returning an array. This I haven't thought to be possible. I made a quick fix, would it be possible for you to test it? If this works, I will publish it right away. |
@RoyLofthus please ignore my last comment. I checked your logs and seems you were pointing to a specific version. This shouldn't be the case. It is late at my place right now, I'll take a better look at this tomorrow. |
Was this issue resolved? Yesterday I was receiving the same error message: After some research, I changed the task version from 1.* to 2.* to have VS 2019 compatibility. I was previously using it for VS 2017 solutions. I believe I got past this error by deleting the DevEnv task and adding a new one. I think I also had the solution file name in the project field after the version change. Which caused other errors. |
also ran into this issue - but for ours, the problem stemmed from having both VS professional and VS enterprise on the same machine |
Also get the same error. This is cause by the function Get-VSPath that fails to narrow down the path of vs2019.
The correct filter should be |
The task started to fail after VS2019 was installed on the build-agent, By looking at the debug-output, it looks like the Get-VsPath method returns paths to both versions, instead of just the Latest. We've tried to specify a specific version, but with same result. Attached is a screenshot of the debug-output
The text was updated successfully, but these errors were encountered: