Skip to content
This repository has been archived by the owner on Dec 8, 2018. It is now read-only.

Move ICompilationException to Diagnostics.Abstractions #220

Closed
pranavkm opened this issue Dec 3, 2015 · 6 comments
Closed

Move ICompilationException to Diagnostics.Abstractions #220

pranavkm opened this issue Dec 3, 2015 · 6 comments
Assignees
Milestone

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Dec 3, 2015

We use ICompilationException as a contract between diagnostics and other middlewares (primarily Mvc) that perform runtime compilation to show a pretty printed compilation failure. Currently the contract for this exception is located in Microsoft.Extensions.CompilationAbstractions. This would allow removing the CompilationAbstractions dependency.

@davidfowl
Copy link
Member

It also means that hosting will end up depending on this weird assembly 😄

@pranavkm
Copy link
Contributor Author

pranavkm commented Dec 3, 2015

Why would hosting need to depend on this assembly?

@Tratcher
Copy link
Member

Tratcher commented Dec 3, 2015

@pranavkm
Copy link
Contributor Author

pranavkm commented Dec 3, 2015

That's meant for compile time exceptions (stuff coming from DNX) which we can leave as is. This was specifically for runtime compilation.

@davidfowl
Copy link
Member

Assigned to you @pranavkm. You'll have to leave a copy in DNX so that nothing breaks while we transition over. You can also remove the compilation error support from the Hosting page.

@pranavkm
Copy link
Contributor Author

pranavkm commented Dec 7, 2015

Yeah - I'm going to rename the namespace for this interface so the current one can co-exist until we transition. For aspnet/Hosting#510, are we simply gutting the code?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants