Is there any way to generate pre-compiled views with EF6 RC1? EF Powertools hasn't been updated so far, and this T4 template (https://entityframework.codeplex.com/workitem/1258) doesnt work either.
Is there any roadmap for making pre-compiled views happen for EF6?
Also, is there support for precompiled views when the Context-Class lives in a different assembly than the assembly containing POCO-entities?
Example:
- ProjectName.Entities (POCO entities, no reference to EF)
- ProjectName.Data (DataContext, reference to EF)
We would like to have the pre-compiled view file living inside the *.Data assembly because we do not want to reference EF from the Entities-Assembly.
By the way, in our team, we do really hope that the next release after EF6 will contain the discussed view generation API, so that we can dynamically create views and store them on the file-system (e.x. in the applications run-time folder).
Startup-Performance is an important area in our rich-client application scenario, and I think EF still needs improvements in this area (by optimizing performance in general and by providing an easy to use api so that caching can be done dynamically in the application).
Thank you!
Comments: Hi, I am glad that you are working on making precompiled views happen for EF6. Of course, the app would need to persist the views to disk and reuse them to achieve a performance benefit. Nevertheless, I think one advantage of caching the view in an external file is that it does not need to be compiled/embedded into the applications assembly. This would save build time and would lead to smaller shipped assemblies (especially if you have a huge model).
Is there any roadmap for making pre-compiled views happen for EF6?
Also, is there support for precompiled views when the Context-Class lives in a different assembly than the assembly containing POCO-entities?
Example:
- ProjectName.Entities (POCO entities, no reference to EF)
- ProjectName.Data (DataContext, reference to EF)
We would like to have the pre-compiled view file living inside the *.Data assembly because we do not want to reference EF from the Entities-Assembly.
By the way, in our team, we do really hope that the next release after EF6 will contain the discussed view generation API, so that we can dynamically create views and store them on the file-system (e.x. in the applications run-time folder).
Startup-Performance is an important area in our rich-client application scenario, and I think EF still needs improvements in this area (by optimizing performance in general and by providing an easy to use api so that caching can be done dynamically in the application).
Thank you!
Comments: Hi, I am glad that you are working on making precompiled views happen for EF6. Of course, the app would need to persist the views to disk and reuse them to achieve a performance benefit. Nevertheless, I think one advantage of caching the view in an external file is that it does not need to be compiled/embedded into the applications assembly. This would save build time and would lead to smaller shipped assemblies (especially if you have a huge model).