E23: Stored Procedures in ASP.Net Boilerplate

[@lovol2]

Thanks for this, very helpful.

[@chewangyolmoo4628]

Your contents have helped me. Thanks for this new great content on abp. Can you please do a video on storing data on both host and tenant database simultaneously using abp?

[@LeeRichardson200]

So glad it helped! Absolutely, I'd love to do one on multi-tenancy. Can you describe that scenario a little further chewant? I'm guessing you don't mean IMayHaveTenant where a record can be on host OR a tenant. Would leaving off IMayHaveTenant or IMustHaveTenant entirely such that a record would effectively be on all tenants and the host solve the problem? Or do you mean leaving on IMustHaveTenant so the record exists for a tenant but disabling the filter so that the host can read it (e.g. `using (_unitOfWorkManager.Current.DisableFilter(AbpDataFilters.MustHaveTenant)) {`). If I'm not understanding please explain further I'd love to include this scenario.

[@chewangyolmoo4628]

@@LeeRichardson200 My current scenario is each tenant will have seperate database and tenant users should be able to access few entities from host database. How can a tenant and its users set reference to host database tables? I want to know how this can be achieved. Previously i was thinking of storing data both on host and tenant db but I think keeping on host is sufficient. Does it require IMustHaveTenant to be implemented? I am relatively new to abp so your help is much appreciated. Thanks.😀

[@mohamedadel-uo2vy]

thanks for video was very interesting i want to ask about if i wanted to add multiple projejects to get many published files (as they are many web api projects in same soulution) how can i do some thing like that in ABP boilerplate? thanks in advance.

[@athalyeakshay09]

This helped me understand for our app. How do we use the same platform for DB First ?

[@LeeRichardson200]

I'm pretty sure that ASP.Net Boilerplate will not work with DB First. The reason is, it gives you a lot of tables for various functionality like authentication and authorization up-front, and it adds that via migrations. Your best bet would be to have a 2nd data context to your existing database. I've done that, and it's a little messy, but doable.