czemacleod / c3d.msbuild.tools.ef6.generateviews Goto Github PK

Thank you so much for providing this. Not only does it help with not needing the Power Tools anymore, but it also means I don't have to worry about remembering to generate mapping views. Can't tell you how many times I spaced that step and broke the build...

Anyway, now that I have the two entries in my csproj file (EntityView and EntityDeploy), the edmx is duplicated in the Solution Explorer. Am I doing something wrong, is there a way around that, or is that just a side effect we'll have to live with?

<EntityDeploy Include="iMISEntities.edmx">
  <Generator>EntityModelCodeGenerator</Generator>
  <LastGenOutput>iMISEntities.Designer.cs</LastGenOutput>
</EntityDeploy>
<EntityView Include="iMISEntities.edmx">
  <Generator>
  </Generator>
  <CustomToolNamespace>Model</CustomToolNamespace>
</EntityView>

Thanks again!

~Justin

I am using code first migrations. In VS2019, I used EF Power Tools to give me an Entity Framework menu on my DBContext class file in the solution explorer.
When I selected Generate Views, it would take about a minute to generate the views. The result was a DBContext.Views.cs file added to the project.

Since EF Power Tools isn't available for VS2022, I am trying to migrate to your build tool. It sounds great but I am not sure I have it installed properly.

Here is what I did:

1. I installed the NuGet package into my MVC Project. I have many projects within the solution. The SkyCourt project is the start up project that is where the MVC app lives. This is also where the migrations live. I have another project called SkyCourt.Models that is where the DBContext class lives. This is where the .Views.cs file used to live.
2. I deleted the .Views.cs file from my project
3. I unloaded the SkyCourt project and edited the file to add the code snippet from the main page of your project.
4. I loaded the project and made a change to the model.
5. I then opened the package manager and ran Add-Migration
6. I then ran Update-Database

Everything went well, but I am not sure that that the Views were created. I have no .edmx in my solution view. And when I did the Udpate-Database, it took about 2 seconds where normally view generation takes about 60 seconds.

I looked in the obj directory for SkyCourt and I do not see anything called EntityViews.

Did I miss something?

Thanks

Any plans on turning this into a C# Source Generator?

We have a DB first context like AcmeContext : DbContext, which is automatically created. We then have a superclass of this with our customisations SuperAcmeContext : AcmeContext. However, the superclass cannot access the generated views because they are sealed.

I think if the views were not sealed OR the DbMappingViewCacheTypeAttribute allowed for a parameterised type then it would work. For example [assembly: DbMappingViewCacheTypeAttribute(SuperAcmeContext,...)

Any ideas if there is a workaround?

Support multiple edmx files in the same project.

• The Task need to be updated for multiple Input and Output files.
• The Target need to handle the multiple output files.