Kestrel has a "special" build:

• It invokes DNX as a post build step
• It relies on compilation modules
• Might (not sure) spin up a new server that's not in proc as part of the tests

cc @cesarbs @halter73

At a minimum, you have to upgrade a few scripts and project.json files just like here: aspnet/Configuration@9cfd22f

cc @muratg

• It invokes DNX as a post build step

I don't think this should be a huge issue. Basically all we need to do is run two command line apps (tools/Microsoft.AspNet.Server.Kestrel.GeneratedCode and tools/Microsoft.AspNet.Server.Kestrel.GeneratedCode) before building the main project.

• It relies on compilation modules

I think we can remove this for now as long as we have a plan to move this to an analyzer.

• Might (not sure) spin up a new server that's not in proc as part of the tests

Why do you think that? I'm pretty sure that's not the case.

I think we can remove this for now as long as we have a plan to move this to an analyzer.

Why do we care about this only in Kestrel? I don't see anything similar in other projects.

We don't actually. We can remove it for now and fix it later. @lodejard wrote it to keep himself in check 😄