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

Use shared compiler in CoreGenerateSatelliteAssemblies #1762

Merged

Conversation

tmeschter
Copy link
Contributor

The CoreGenerateSatelliteAssemblies target uses the Csc task to
create satellite assemblies. We can greatly speed up the creation of
these assemblies by telling Csc to use the shared compiler server if
it is available, rather than spinning up a new copy of csc.exe for every
satellite.

The `CoreGenerateSatelliteAssemblies` target uses the `Csc` task to
create satellite assemblies. We can greatly speed up the creation of
these assemblies by telling `Csc` to use the shared compiler server if
it is available, rather than spinning up a new copy of csc.exe for every
satellite.
@tmeschter
Copy link
Contributor Author

For an example of the speed up, when using XliffTasks in the dotnet/roslyn repo without this change the build takes ten minutes. With this change it takes two and a half minutes.

@nguerrera
Copy link
Contributor

nguerrera commented Nov 21, 2017

Cool. Until your recent msbuild change, this code could only be used on core. And there was no compiler server on core until just recently either. But neither are true now and this will be a huge win for core (and not just when opting in to use core generate on non-core as you're doing for roslyn now). Great timing! :)

@nguerrera nguerrera merged commit 8c5d7a7 into dotnet:master Nov 21, 2017
JL03-Yue pushed a commit that referenced this pull request Mar 19, 2024
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