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

Autodiscovery and compilation of Razor views via embedded providers #5144

Closed
danroth27 opened this issue Aug 15, 2016 · 3 comments
Closed

Autodiscovery and compilation of Razor views via embedded providers #5144

danroth27 opened this issue Aug 15, 2016 · 3 comments

Comments

@danroth27
Copy link
Member

Consider supporting Razor views as embedded resources out of the box.

@Antaris
Copy link

Antaris commented Sep 1, 2016

I'd be interested to know how you plan to enable debugging for these embedded views? I'm already supporting embedded views in my ASP.NET Core app, but can't easily debug them.

@pranavkm
Copy link
Contributor

pranavkm commented Sep 2, 2016

@Antaris an option we were exploring here was to rely on a Roslyn feature that would allow us to embed sources for views in generated pdbs. Here's the discussion for it - dotnet/roslyn#12625. Note: the feature hasn't landed and requires follow up work in the debugger to know how to get to these sources, so it'll be a while for the feature to light up.

At present, you have to point to files on disk for the debugger to find them. You could consider using a PhysicalFileProvider that points to the source project when developing locally and switching to an embedded one when you're deploying.

@Eilon
Copy link
Member

Eilon commented Feb 2, 2017

Given that we have good support for pre-compiling Razor views, we are closing this issue.

@Eilon Eilon closed this as completed Feb 2, 2017
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