You dont :) So our process uses GECO (<a class="postlink" href="https://github.com/iQuarc/Geco">https://github.com/iQuarc/Geco</a>) to generate our code, we ended up creating everything as partials so that way we dont modify the ABP files directly. This helps with merging, especially when you create over 5k files per generation :). For the UI pages we created a folder called "Generated" the generator puts those files there, if we then "modify" them, we move it to the root folder that way if we generate later we dont touch the modified files and can now diff the two files.
Wont you have the same issue if you regenerate app services and such also and added custom methods and dont partial them?
I did a little write up here:
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/1262">https://github.com/aspnetzero/aspnet-ze ... ssues/1262</a>
What are you trying to prevent? Because the next action they take should trigger a permission check which would direct them away anyways.
You could probably do something with signalR or the event bus: <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Javascript-API/Event-Bus">https://aspnetboilerplate.com/Pages/Doc ... /Event-Bus</a>
Again. Your explanation isnt valid for most web sites. I make a user inactive, he then tries to goto a another page on the site, he will be directed away, even if they try to edit a record it will come back as not valid. So again what are you really trying to prevent, seeing content. At some point the user will navigate away or session will close even if idle and the user comes back they wont be active. You want to force close a session/force a redirect, so you need to implement signlalR or the even listener.
How did you make your razor pages? Are you inheriting from the base ABPRazorPage? or just Page? I was looking at going down this path also, but I got the PageContext is not valid if I use the abprazorpage and if I use Page I dont get all the localization and stuff and havent had time to go back to work thru making a new class and stuff :) I did add a ticket a while ago about this since I think it would help alot with keep code separated and migrations easier.
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/1189">https://github.com/aspnetzero/aspnet-ze ... ssues/1189</a>
It looks pretty easy to me. <a class="postlink" href="https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net-core">https://docs.microsoft.com/en-us/azure/ ... p-net-core</a>
Then you install the nuget package for logging <a class="postlink" href="https://github.com/Microsoft/ApplicationInsights-dotnet-logging">https://github.com/Microsoft/Applicatio ... et-logging</a>
use something like windir and compare the two extracted solutions
See: <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/1336">https://github.com/aspnetzero/aspnet-ze ... ssues/1336</a>
We use SQL just fine. Just generate a new user with a default password you want to use, take the hash and use it. Set user to change password on login. Dont do any of this looping in C# crap, waste of time for a 1x import.
There is a table in the host that you also need to write the newly created user account info to also.
If you make a new user, just look in all the user tables in the tenant and host to trace what needs to be done.
Our DBAs load our tenant dbs with users/permissions/roles for all the internal people that work on that tenants account and we have no issues. (Now we get to add WsFederation so another table to write to if you want to do that too :) )
In corporate usage its very normal. You segment clients data to own databases for isolation, internal users need to access multiple clients data to perform tasks. Having multiple accounts is annoying especially since you need to maintain roles and permissions cross clients, and when you on board a new client configure again. Ideally you would have to have a master set of users and limit their client access.