Skip to content

Conversation

@robertpi
Copy link
Contributor

@robertpi robertpi commented Aug 25, 2020

Description

Adds the paths for VS2019 for vstest exe.

Solves #2540

@matthid
Copy link
Member

matthid commented Sep 3, 2020

Thanks for sending in a PR!

Yes makes sense to add this (and I probably can merge it as-is), but couldn't we copy some of the vswhere logic from MSBuild to include future VS version out of the box?

@matthid matthid changed the title add paths for VS2019 add VSTEST paths for VS2019 Sep 3, 2020
@robertpi
Copy link
Contributor Author

robertpi commented Sep 3, 2020

I'm new to the FAKE code base, so I simply extended the solution that was already implemented.

Agree replacing what's been done with a call to vswhere makes sense, but seeing this PR merged is more like to spur my motivation to contribute than seeing it rejected.

@github-actions
Copy link
Contributor

There has not been any activity in this pull request for the last 3 months so it will be closed in 14 days if there is no activity.

@github-actions github-actions bot added the stale label Dec 10, 2020
@github-actions github-actions bot closed this Dec 24, 2020
@spencer-wcri
Copy link

Is there some reason this was never merged?

@xperiandri
Copy link
Collaborator

I don't know. Let's resurrect this and update to support 2022 and MSTest v3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants