I'm using efg to generate two different DbContexts, one regular read/write and a second one for read only access.
For this I have two separate .yml-configuration files and I run using efg -f standard-context.yml
The problem is that when I do this, the generator finds the read only DbContext first, and tries to rename it to the standard context name.
I Rename Context Class'PmMarknadSyncDbContext' to 'MarknadReadOnlyDbContext'.
My solution today is to do the generation outside of my project folder and the manually replace the files. But then I loose changes I made outside of #region
I'm using
efgto generate two different DbContexts, one regular read/write and a second one for read only access.For this I have two separate .yml-configuration files and I run using
efg -f standard-context.ymlThe problem is that when I do this, the generator finds the read only DbContext first, and tries to rename it to the standard context name.
I Rename Context Class'PmMarknadSyncDbContext' to 'MarknadReadOnlyDbContext'.My solution today is to do the generation outside of my project folder and the manually replace the files. But then I loose changes I made outside of
#region