Hi,
Ok, my email is: shiwei.liang@volosoft.com
Hi,
You need to customize the application module: https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Guide
Do you have the required files that needed to add on our old project
It's hard to explain. Because your license has the source code, you can download different versions of the module source code to compare. you can clearly see the differences between different versions of code.
I recommend that you replace the module package reference with a local reference. You can do it through suite:
In this way, you can copy the file(changes) from the source code of the new version of the module to your local module, which will reduce your time.
Hi,
ABP uses the AssemblyLoadContext
to load assembly.
You can check the Microsoft's document: https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/understanding-assemblyloadcontext https://learn.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblyloadcontext?view=net-7.0
It is not possible to load multiple versions of the runtime in a single process.
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblyloadcontext?view=net-7.0#technical-challenges The document mentions that you can't load different versions in a single process.
You can try to use resolving
event instead of AppDomain.CurrentDomain.AssemblyResolve
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblyloadcontext.resolving?view=net-7.0#system-runtime-loader-assemblyloadcontext-resolving
Hi,
This has nothing to do with ABP actually, you can check Microsoft's documentation https://learn.microsoft.com/en-us/aspnet/core/security/docker-https?view=aspnetcore-7.0 https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-docker-compose?UI=NG&DB=EF&Tiered=Yes
Hi,
ABP already supports Authenticator in version 7.3. https://docs.abp.io/en/commercial/latest/modules/identity/two-factor-authentication#verification-providers
I suggest that you upgrade the version instead of manually adding this feature to the old project.
If you still want to implement this function in the old project, you can download the source code of the identity and account modules and apply it to your project. (It's really a lot of work that's why I suggest you upgrade the version).
Hi,
Is there any error stack?
Hi,
Unfortunately, you can't do this, because the application layer can't access httpcontext.
You can write a middleware to modify the http status code.
Hi,
It's a problem, we will fix it. your ticket refunded
You can try to override the abp.ResourceLoader._loadScript
javascript method:
abp.ResourceLoader._loadScript = function (url, loadCallback, failCallback) {
if(url.startsWith("/Pages/FileManagement")){
url = abp.appPath + url.substring(1);
}
var nonce = document.body.nonce || document.body.getAttribute('nonce');
_loadFromUrl(url, loadCallback, failCallback, function (urlInfo) {
$.get({
url: url,
dataType: 'text'
})
.done(function (script) {
if(nonce){
$.globalEval(script, { nonce: nonce});
}else{
$.globalEval(script);
}
urlInfo.succeed();
})
.fail(function () {
urlInfo.failed();
});
});
};
Hi,
You should manually assign the ID
when creating the entity, for example:
https://docs.abp.io/en/abp/latest/Best-Practices/Entities#example https://github.com/abpframework/abp/blob/dev/modules/identity/src/Volo.Abp.Identity.Application/Volo/Abp/Identity/IdentityUserAppService.cs#L78
Hi,
I have enabled ABP framework to post message to Kafka using the builtin mechanism (not PublishAsync()).
So are you manually using the Kafka API to post messages instead of EventBus
?
I may want to publish the message only if say the status = "ACTIVE" or IsExpired = false
Can you explain in detail? thanks.