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

Move IRazorViewEngineFileProviderAccessor and ExpressionRewriter to the public namespace #4938

Closed
DavidEmanuelsen opened this issue Jun 30, 2016 · 5 comments

Comments

@DavidEmanuelsen
Copy link

DavidEmanuelsen commented Jun 30, 2016

An application we're building has ended up needing to implement a modified version of DefaultRoslynCompilationService to avoid caching of the list of compilation references. In the modified version we still depend (as far as I can see) on IRazorViewEngineFileProviderAccessor and ExpressionRewriter which are both in the .Internal-namespace.

Is there any chance this can be moved to the public namespace to minimize risks of breaking changes in the future?

See #4497 for history

@Eilon
Copy link
Member

Eilon commented Dec 20, 2016

@NTaylorMullen @pranavkm @rynowak thoughts on this? Would it make sense to move these types to a public namespace?

@davidfowl
Copy link
Member

No, if you ended up rewriting the default service then we have a gap somewhere in our extensibility.

@rynowak
Copy link
Member

rynowak commented Dec 21, 2016

@davidfowl - we did identify a gap here... remember when we designed compilation factory and reference manager?

We should make an abstraction for https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Razor/Internal/RazorReferenceManager.cs and make it public, that's the part you're asking for right @DavidEmanuelsen ?

@Eilon
Copy link
Member

Eilon commented May 13, 2017

@rynowak I'm parking this on your plate. If you think we can get this in, let's do it, but if not, I think we should close it.

rynowak added a commit that referenced this issue May 25, 2017
Fix for #4938. This change makes the reference manager public and
documented so that it can be replaced.
rynowak added a commit that referenced this issue May 26, 2017
Fix for #4938. This change makes the reference manager public and
documented so that it can be replaced.
@rynowak
Copy link
Member

rynowak commented May 26, 2017

c3f7613

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

4 participants