MSBUILD Server

[donJoseLuis]

Deliver the MSBUILD server requirements:

1. Server behavior: MSBuild is capable of running its scheduler and the "in-proc" node in a persistent server process. The process implements a communication mechanism to be able to accept build requests from other processes and return console logging.
2. Client behavior: The .NET CLI implements a communication mechanism to send build requests to MSBuild server instead of loading Microsoft.Build into the CLI process.
3. Full console fidelity: Console output of the client is indistinguishable from the current behavior.
4. Configurability: It is possible to opt out of the new behavior in case it causes unexpected issues.
5. Performance: The feature results in a significant speed up of the CLI inner loop. Incremental build of a simple ASP.NET Core app is at least 3x faster.

Child tasks:

• Design client-server communication protocol
• Implement a new nodetype for the server process
• Implement communication protocol in server
• Implement communication protocol in the client library
• Introduce a client-side activation/communication library
• Cover MSBuild server with tests
• Consume the client library in dotnet CLI
• MSBuild Server instrumentation
• Memory Leak with MSBuild Server
• Investigate MSBuild Server for memory leaks.
• MSBUILD Server: cancellation.
• MSBuild server needs to know Client Console configuration
• Make MSBuild client API experimental

estimates

• 2 weeks for client work
• 2 for server work
• 3 weeks for remaining things
• 2 weeks buffer