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

MVC precompilation design notes 5/12/2015 #2551

Closed
@Eilon

Description

@Eilon

Today we had a design meeting with: @Alxandr @danroth27 @DamianEdwards @davidfowl @dougbu @lodejard @pranavkm @NTaylorMullen @ToddGrun @muratg

Please add your own thoughts as comments to this thread.

Agenda


Meeting notes

  1. Precompilation should not be enabled by default in project templates (it can exist, but should not be used in DTH scenarios)
  2. Precompilation is for:
    a. Server optimization (especially for large sites)
    b. Avoiding using a compiler on the server, which is good for security purposes
    c. Components with everything compiled in (including views) and ready to go
  3. Precompilation should not require any physical files on disk
  4. Precompilation behaviors:
    a. All view locators would always check for a file “on disk” (whether it’s physical or virtual)
    b. Precompilation would embed at least empty placeholder files into a virtual embedded file system
    c. You could also have a case where you embed the full files into the embedded file system, but also have precompilation enabled. You would then have updateable precompilation.
  5. We should use precompilation (or something else that’s similar! E.g. a Roslyn Analyzer?) to enable showing Razor errors in VS
  6. Question: Should any of these behaviors change while in DesignTimeHost (DTH)?
  7. Question: How do you enable precompilation? Today it’s a CompileModule. Should it be something else?
  8. Action item: Need to dig into exactly why the tag helper scenario is broken, and address that specifically.
  9. Action item: Should we remove Roslyn dependency from Razor? (Not interesting right now)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions