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

Update to MSBuild project model and fix for cross-targeting projects #707

Merged

Conversation

DustinCampbell
Copy link
Contributor

Lots of changes here, but the key pieces are:

  1. The MSBuild packages are updated to the latest.
  2. We now include the right set of NuGet packages that we'll need to perform restore.
  3. We include the NuGet.Build.Tasks package in the msbuild folder.
  4. MSBuild tests are enabled (hope they pass this time!)
  5. We check to see if there are multiple TFMs and pick one prior to running the "ResolveReferences" task. (Otherwise, we can't process cross-targeting MSBuild projects.)
  6. The MSBuild project model includes the list of TFMs specified in the project file.
  7. The MSBuild project model includes the output path of the project file.

@DustinCampbell
Copy link
Contributor Author

cc @david-driscoll

@DustinCampbell
Copy link
Contributor Author

I wonder if this is ready to merge into dev?

@DustinCampbell
Copy link
Contributor Author

That ran locally grumble

@DustinCampbell DustinCampbell force-pushed the update-project-model branch 3 times, most recently from 4c762c7 to b361033 Compare December 15, 2016 15:29
Copy link
Member

@david-driscoll david-driscoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

{
// For now, we'll just pick the first target framework. Eventually, we'll need to
// do better and potentially allow OmniSharp hosts to select a target framework.
targetFramework = targetFrameworks[0];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the past we've exposed this on each request, but a dedicated endpoint would be ideal.

What about support in VScode? Any UI that might be setup?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eventually, yeah. Providing this on each request might prove very expensive.

@DustinCampbell DustinCampbell force-pushed the update-project-model branch 4 times, most recently from 36ce9a2 to ce473ec Compare December 15, 2016 18:59
@DustinCampbell DustinCampbell force-pushed the update-project-model branch 8 times, most recently from d601450 to 28ec64c Compare December 15, 2016 20:56
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.

2 participants