Hi,
could you please share the full steps to reproduce ? thanks.
Hi,
ABP will not be verified online in the production environment
Hi,
you can override the register model.
[Dependency(ReplaceServices = true)]
[ExposeServices(typeof(RegisterModel))]
public class MyRegisterModel : RegisterModel
{
public MyRegisterModel(
IAuthenticationSchemeProvider schemeProvider,
IOptions<AbpAccountOptions> accountOptions,
IAccountExternalProviderAppService accountExternalProviderAppService,
ICurrentPrincipalAccessor currentPrincipalAccessor,
IHttpClientFactory httpClientFactory) : base(schemeProvider, accountOptions, accountExternalProviderAppService, currentPrincipalAccessor, httpClientFactory)
{
}
protected override Task<IdentityUser> RegisterLocalUserAsync()
{
//.....
}
protected override Task<IdentityUser> RegisterExternalUserAsync(ExternalLoginInfo externalLoginInfo, string userName, string emailAddress)
{
//.....
}
}
Hi,
Can you share the full applicaation error logs
Hi,
Okay, I will check it.
Hi,
I think it can't be done, It can intercept the local cluster
Sorry, I give the wrong answer, It can intercept local and remote clusters
yes, you can see the video here:
Hi,
Please send code to jsanchez@innovain.com
Sorry, i didn't get it
Hi,
Add _ViewImports.cshtml
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bootstrap
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bundling
Hi,
I understand that, In fact, you don't have to worry about it, the main difference between the old and the new template is the configuration file. If you want, you can absolutely use the new template to develop your application. The beta phase I mentioned is the studio, not the template.
Hi,
Here are some relevant explanations.
https://abp.io/docs/latest/cli/differences-between-old-and-new-cli
Thanks for that. What is the timeline on this?
December 31, 2024 you can see the milestone here https://github.com/abpframework/abp/milestone/107
Based on other posts here, I believe that we are not the only ones that are currently confused / frustrated about what CLI / templates to actually use for new projects intended for production, especially considering that ABP Studio (and the new CLI I think) is still in beta. I hope ABP will be able to address this situation better going forward as I feel that we have been stuck in a holding pattern for quite some time now.
Yes, the studio is still in the beta phase and almost stable. If you want a stable template, I still recommend you use the old CLI.
In fact, you can use the new template and copy the Docker configuration from the old template to the new template. It's a little ugly, but it works.