Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "MBTLGPLC19"

Hi,

How can I find the sample IdentityServerClient indicated in the documentation:
https://docs.aspnetzero.com/en/aspnet-core-mvc/latest/Infrastructure-Core-Mvc-Identity-Server4-Integration#testing-with-mvc-client

Thanks

Following the tip in https://support.aspnetzero.com/QA/Questions/4049#answer-447ec9e8-b664-4f5a-b75f-313a2a2236f3, I'm trying to do the same thing in an asp.net core 2.2 solution (redirect to a page if the user hasn't the permission, but is already logged). I have tried to implement my AbpMvcAuthorizeFilter class, but without sucess (I cannot resolve the AuthorizationContext sucessfully, even after adding all asp.net mvc dependences). I tried to create the middleware for changing the behavior, but I cannot see the status code forbidden or unauthorized after executing the call to be able to redirect as I want. Another thing: there's someway to avoid to hit the middleware's method everytime ? Like, if we already validated that the user has permission, we can leave the middleware.

Hello, I'm creating an asp.net core application where we will be injecting different plugins. In https://support.aspnetzero.com/QA/Questions/2513 I saw that ABP is able to load the plugin dependencies if they are in the same folder.

In our case, each plugin can (and will) have its own dependencies at some time. They are going to be developped, kept and released in different timelines (so we cannot update and release all of them at once). So we will have the following scenarios:

a) 2 Plugins being used at the same time that depends of different versions of the same dll APPLICATION PLUGIN_A |-- DLL_A V_1.0.0 PLUGIN_B |-- DLL_A V_3.0.0

a.2) The plugin_a was updated, so now the 2 of them run with the same dll version APPLICATION PLUGIN_A |-- DLL_A V_3.0.0 PLUGIN_B |-- DLL_A V_3.0.0

b) Plugin with a different dll version than the one we are using in the application APPLICATION |-- DLL_B V.2.0.0 PLUGIN_A |-- DLL_B V.1.0.0

b.1) Plugin was updated so it now uses the same dll version in the application APPLICATION |-- DLL_B V.2.0.0 PLUGIN_A |-- DLL_B V.2.0.0

So, how I can accomplish this? By creating plugin subfolders and adding the plugin and its dependencies there (even if it's lower than the one we have in the bin ?) and ABP will do the job for us? Or by embedding the plugin's dependencies in its dll and loading it? (If so, can you provide a sample or some code where we do this using ABP ?)

Showing 1 to 3 of 3 entries