-
Notifications
You must be signed in to change notification settings - Fork 10.3k
FileProviders MvcRazorRuntimeCompilationOptions vs RazorViewEngineOptions #14221
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
Comments
I have discovered that in order to work I have to deactivate other services, ok |
I'm experiencing the same problem and couldn't understand your solution. Can it be any clearer? |
Yes, it does not work anymore as in last net core 2.2 was good -> In asp.net core 3 In order to work you have to add the CompileOnRuntime and deactivate some functionalities In past version 2.2 it was working |
Same problem for me after migrating to asp.net core 3.0. Any workaround ? |
Thanks for contacting us, @DiegoStefanon. |
It looks like AddMvcRazorRuntimeCompilation has been renamed to AddRazorRuntimeCompilation. I cannot comment on aspnet/Announcements#343. |
Also same problem after migrating from core 2.2 to asp.net core 3.0. |
We use FileProviders to pointing out views in different modules. When Project is compiled in Release mode views are copied to the main project. We do not use compilation. In 3.0 it is not working. Why? Why? Why? It only works as the views compilation is enabled. Otherwise, he can't see even the paths given by ViewLocationExpanders. |
Describe the bug
in core 3.rc1 is not working anymore ->
services.Configure<MvcRazorRuntimeCompilationOptions>(opts =>
opts.FileProviders.Add(fp)
);
in core 2.2 was good ->
RazorViewEngineOptions FileProviders.Add was working
Expected behavior
In asp.net core 3 rc1
RazorViewEngineOptions has no more FileProviders property
so using the new one MvcRazorRuntimeCompilationOptions is not working anymore
Thanks
The text was updated successfully, but these errors were encountered: