Skip to content

Unify VS Setup - #484

Merged
jasonmalinowski merged 4 commits into
dotnet:masterfrom
jasonmalinowski:unify-vs-setup
Feb 13, 2015
Merged

Unify VS Setup#484
jasonmalinowski merged 4 commits into
dotnet:masterfrom
jasonmalinowski:unify-vs-setup

Conversation

@jasonmalinowski

Copy link
Copy Markdown
Member

A change to move some of the stuff in our language service integration to GitHub.

@dnfclas

dnfclas commented Feb 13, 2015

Copy link
Copy Markdown

Hi @jasonmalinowski, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@jaredpar

Copy link
Copy Markdown
Member

LGTM

@dnfclas

dnfclas commented Feb 13, 2015

Copy link
Copy Markdown

@jasonmalinowski, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

@tmeschter

Copy link
Copy Markdown
Contributor

I updated the Commands.vsct file this morning, so you may want to pull in those changes before you move it to open.

This change moves the contents of VisualStudioSetup into the open,
merging with (and consuming) VisualStudioComponents. The Components/
Setup split originally existed as a way to allow multiple Roslyn-using
components to have a single source of truth of the MEF exports. This
meant you could have either the interactive window, language services,
or both installed and everything worked. This was important when we
were atop Visual Studio 2013, but now that we're integrated it's buying
us nothing.

The VSIX ID from VisualStudioComponents is preserved so that way any
extensions that declared a dependency on it will still work.
@jasonmalinowski

Copy link
Copy Markdown
Member Author

@tmeschter Can you verify I've consumed the update?

@tmeschter

Copy link
Copy Markdown
Contributor

Looks like it's all up to date.
👍

@jaredpar

Copy link
Copy Markdown
Member

LGTM

jasonmalinowski added a commit that referenced this pull request Feb 13, 2015
@jasonmalinowski
jasonmalinowski merged commit 39390b3 into dotnet:master Feb 13, 2015
@jasonmalinowski
jasonmalinowski deleted the unify-vs-setup branch February 24, 2015 23:44
dibarbet pushed a commit that referenced this pull request Aug 18, 2026
Include framework references except for package based frameworks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants