Skip to content
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

MSBuild unit test refactoring #694

Conversation

DustinCampbell
Copy link
Contributor

This change adds the first MSBuild project unit test and unifies the "sample projects" into a top-level folder called "test-assets"

…est!)

This is a fairly significant change in that it adds our first MSBuild
project test. This requires some gymnastics to ensure that MSBuild.exe can
to set up MSBuild's build environment. In the tests, we set the
MSBUILD_EXE_PATH environment variable to properly locate MSBuild during
test runs.
@DustinCampbell
Copy link
Contributor Author

It's likely that the CI build will fail when running tests for MSBuild on net46. I'm guessing I'll need to disable that for now.

@DustinCampbell
Copy link
Contributor Author

Ugh. The new MSBuild unit test fails on OSX/Linux because it needs to be restored first to get the targets and packages. However, because we build with an older version of the .NET CLI, restore won't work for the csproj. 😞

@DustinCampbell DustinCampbell merged commit e3eb825 into OmniSharp:new-msbuild Dec 6, 2016
@DustinCampbell DustinCampbell deleted the handle-multiple-frameworks branch January 19, 2017 14:10
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.

1 participant