Closed williambowsher closed 5 years ago
Hi thanks for pointing out the docs need to be updated.
I recommend creating a dummy tenant info like in this sample:
It's ok I have worked around the issue and have it all functioning now.
Thanks for responding, you can close the ticket.
On Tue, 15 Oct 2019, 15:59 Andrew White, notifications@github.com wrote:
Hi thanks for pointing out the docs need to be updated.
I recommend creating a dummy tenant info like in this sample:
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Finbuckle/Finbuckle.MultiTenant/issues/192?email_source=notifications&email_token=AFICAZYTKBC2IDR264X7HCTQOXEDRA5CNFSM4JAXWR42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBI3PVY#issuecomment-542226391, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFICAZYVQQ4F6QBCOO4PXADQOXEDRANCNFSM4JAXWR4Q .
Thanks for the help, but I have implemented a slightly different solution as I have a separate tenant management application.
Thanks for all the hard work with Finbuckle, keep it up.
Regards
I am trying to use the MultitenantDbContext and the documented constructor that only takes a connectionString, but there is no such constructor.
Is there anyway of creating a DesignTime Db Context so that I can process my Migrations?