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.

Sign up for GitHub

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

Jump to bottom

Consider exposing Microsoft.Build internals to MSBuild.exe #5041

Open
rainersigwald opened this issue Jan 9, 2020 · 0 comments
Open

Consider exposing Microsoft.Build internals to MSBuild.exe #5041

rainersigwald opened this issue Jan 9, 2020 · 0 comments
Labels
Area: Engine Issues impacting the core execution of targets and tasks. triaged
Milestone
Backlog

Comments

@rainersigwald
Copy link
Member

Today, shared source causes many of the same types to be compiled into Microsoft.Build.dll and MSBuild.exe. That caused a lot of confusion here: #4916 (comment).

We should figure out if there's a strong reason not to just let MSBuild see Microsoft.Build's internals, which would allow us to remove much of the double-compilation.
@rainersigwald rainersigwald added the Area: Engine Issues impacting the core execution of targets and tasks. label Jan 9, 2020
@rainersigwald rainersigwald added this to the Backlog milestone Jan 9, 2020
rainersigwald added a commit to rainersigwald/msbuild that referenced this issue Jan 9, 2020
@rainersigwald
Clarify comment about MSBuildLoadContext test
f561312 
The confusing situation can be resolved by an IVT change, filed as dotnet#5041.
Forgind pushed a commit to Forgind/msbuild that referenced this issue Feb 3, 2020
@rainersigwald @Forgind
Clarify comment about MSBuildLoadContext test
cf3db72 
The confusing situation can be resolved by an IVT change, filed as dotnet#5041.
@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Engine Issues impacting the core execution of targets and tasks. triaged
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@rainersigwald @AR-May