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

Changes do not get deployed to the Roslyn hive with CTP 6 #1041

Closed
EricArndt opened this issue Mar 5, 2015 · 4 comments
Closed

Changes do not get deployed to the Roslyn hive with CTP 6 #1041

EricArndt opened this issue Mar 5, 2015 · 4 comments
Assignees
Labels
Area-Infrastructure Resolution-Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on. Verification Not Required
Milestone

Comments

@EricArndt
Copy link

When trying to fix #780, I was unable to see any of the changes I had made in the Roslyn hive. When I submitted the pull request to test it on the build machine, tests failed in such a way that showed that the changes I made did indeed have an effect. You can see this on the pull request for the issue (#984). Here is what I see in the Roslyn Hive with the changes in the pull request:

image

@jaredpar
Copy link
Member

jaredpar commented Mar 9, 2015

Hey @EricArndt,

Thanks for taking the time to report this issue. Unfortunately at this time there is no supported way for customers to deploy the changes made above the Workspaces layer to the installation of VS 2015 on their machine. We understand this is a decidedly bad place to be and it’s one that we are working hard to remedy. The solution will hopefully come in the VS 2015 Update 1 time frame.

The underlying issue is that it’s not possible to override MEF components that ship in the Visual Studio box with a MEF component in a developer hive. Visual Studio will always prefer the in the box component. Virtually everything above Workspaces layer is a MEF component and can’t be dogfooded by customers.

Fixing this though is unfortunately something Roslyn does not directly control. It involves work from a number of teams and it’s unlikely it will all be done in time for RTM.

@romanov
Copy link

romanov commented Mar 29, 2015

@jaredpar
Copy link
Member

@romanov that would because it's included in the workspaces layer.

@petr-k
Copy link
Contributor

petr-k commented May 12, 2015

@jaredpar If that's the unfortunate case, is there an unsupported way of doing this?

@amcasey amcasey added Resolution-Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on. Verification Not Required labels Jun 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure Resolution-Won't Fix A real bug, but Triage feels that the issue is not impactful enough to spend time on. Verification Not Required
Projects
None yet
Development

No branches or pull requests

8 participants