Activities of "brauerj@gc.adventist.org"

It looks like something very important was recently removed from ABP! The ability to scaffold out a new site with a specific version!!! I highly depend on this capability. Having to upgrade my entire site just to integrate some new code from a scaffolded project is not acceptable. The old CLI has --version. Where is the ability to select which version is used for building code in the new ABP cli/studio?

• ABP Framework version: v9.0.3
• UI Type: Blazor Server
• Sub Modules
• Database System: EF Core (SQL Server)

I'm trying to use ABP Suite to Generate a previously generated entity in a sub module project but it is giving me the error

Cannot find "Volo.Abp.Commercial.SuiteTemplates.dll". ABP Suite cannot find it in any sub folders of C:\Users\UserName\Source\repos\Project\modules\Project.SubModule

I tried adding <PackageReference Include="Volo.Abp.Commercial.SuiteTemplates" Version="9.0.3" /> to the domain project but that didn't help!

I even added

[DependsOn(typeof(VoloAbpCommercialSuiteTemplatesModule))]
...
public class My*****DomainModule : AbpModule

using ABP Suite v9.0.3.

• ABP Framework version: v9.09
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Steps to reproduce the issue:

1. Start or restart application in Visual Studio using the Project (rather than IIS Express)
2. The command line runs but hangs or delays for a long time at:

[14:13:53 DBG] Started background worker: Volo.Abp.BackgroundJobs.BackgroundJobWorker
[14:13:53 DBG] Started background worker: Volo.Abp.Identity.Session.IdentitySessionCleanupBackgroundWorker
[14:13:53 DBG] Started background worker: Volo.Abp.OpenIddict.Tokens.TokenCleanupBackgroundWorker
[14:13:54 DBG] Started background worker: Volo.Abp.AuditLogging.ExpiredAuditLogDeleterWorker

Restarting AGAIN (sometimes several times) can fix it.

• ABP Framework version: v9.0.3
• UI Type:Blazor Server
• Database System: EF Core (SQL Server)

I"m trying to add signout functionality to my ABP app which uses Azure AD/Entra to authenticate. My config looks like:

  sAuth.AddOpenIdConnect("AzureAD", "Microsoft/365", options =>
  {
      options.Authority = "https://login.microsoftonline.com/" + configuration["auth:AzureAd:TenantId"] + "/v2.0/"; 
      options.ClientId = configuration["auth:AzureAd:ClientId"];
      options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
      options.CallbackPath = configuration["auth:AzureAd:CallbackPath"];
      options.ClientSecret = configuration["auth:AzureAd:ClientSecret"]; 
      options.RequireHttpsMetadata = false; 
      options.SaveTokens = true; 
      options.GetClaimsFromUserInfoEndpoint = true;
      options.Scope.Add("email"); 
      options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
  }

I added the following class and that successfully enabled users to "sign out" but what I actually want is for users to be able to switch users. I do NOT want to see the Microsoft "Pick and account" dialog asking "Which account do you want to sign out of?" I tried adding redirect as you see below but that didn't help.

[Dependency(ReplaceServices = true)]
[ExposeServices(typeof(LogoutModel))]
public class CustomLogoutModel : LogoutModel
{
    public override async Task<IActionResult> OnGetAsync()
    {
        if (CurrentUser.IsAuthenticated)
        {
            await IdentitySecurityLogManager.SaveAsync(new IdentitySecurityLogContext
            {
                Identity = IdentitySecurityLogIdentityConsts.Identity,
                Action = IdentitySecurityLogActionConsts.Logout
            });
        }
        //
        await SignInManager.SignOutAsync();
        await HttpContext.SignOutAsync(ConfirmUserModel.ConfirmUserScheme);
        await HttpContext.SignOutAsync(ChangePasswordModel.ChangePasswordScheme);

        //return SignOut("AzureAD");
        var callbackUrl = Url.Page("/Account/Logout", pageHandler: null, values: null, protocol: Request.Scheme);
        var properties = new AuthenticationProperties
        {
            RedirectUri = callbackUrl
        };

        return SignOut(properties, "AzureAD");
    }
}

I just want to let the users sign in again with another user.

• ABP Framework version: v8.1.5
• UI Type: Blazor Server (Basic Theme)
• Database System: EF Core (SQL Server)
• Steps to reproduce the issue:

1. Navigate to First Menu with a sub menu
2. Navigate to Second Menu without clicking again on First Menu.
3. Now they are both open and overlapping each other!

It looks like your CloudFlare configuration is preventing my builds from running on Azure DevOps!!

dotnet restore GcIprs.Main.sln C:\Program Files\dotnet\sdk\8.0.101\NuGet.targets(156,5): error : Unable to load the service index for source https://nuget.abp.io/******/v3/index.json. [C:\azagent\azurebuild1_work\5\s\GcIprs.Main.sln] C:\Program Files\dotnet\sdk\8.0.101\NuGet.targets(156,5): error : Response status code does not indicate success: 403 (Forbidden). [C:\azagent\azurebuild1_work\5\s\GcIprs.Main.sln]

Please help!! I can't deploy new versions.

Why does this not work? According to https://abp.io/docs/latest/ui-themes/lepton-x it should work.

PS C:\Development\abp-Leptonx> abp get-source Volo.Abp.LeptonXTheme ABP CLI 9.0.0 Downloading source code of Volo.Abp.LeptonXTheme (Latest) Output folder: C:\Development\abp-Leptonx Module not found! System.Exception: Module not found! at Volo.Abp.Cli.ProjectBuilding.ModuleInfoProvider.GetAsync(String name) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleInfoProvider.cs:line 41 at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.GetModuleInfoAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 112 at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 46 at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 36 at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 171 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 77 Unhandled exception. System.Exception: Module not found! at Volo.Abp.Cli.ProjectBuilding.ModuleInfoProvider.GetAsync(String name) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleInfoProvider.cs:line 41 at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.GetModuleInfoAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 112 at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 46 at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 36 at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 171 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 77 at Volo.Abp.Cli.Program.Main(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli\Volo\Abp\Cli\Program.cs:line 43 at Volo.Abp.Cli.Program.<Main>(String[] args)

• ABP Framework version: v8.1.2
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no

I have a Blazor control with javascript depencies that is not functioning on live but does on dev, and I'm wondering if it is related to this error which I am seeing on live but not on dev. Other than that I haven't noticed any other issues. Other Javascript seems to be functioning...

Blazor.BasicTheme.Global.BB84A929188038BEBAC9737CB262B16F.js?_v=638518224531532540:31         
GET https://[livesiteurl]/__bundles/themes/silver/theme.js net::ERR_ABORTED 404 (Not Found)

In the logs I also see other /__bundles/ URLs giving 404 errors.

Suggestions?

Thanks,

Jonathan

• ABP Framework version: v8.1.2
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no

There seems to be an issue with the logic in modules\account\src\Volo.Abp.Account.Web\Pages\Account\Register.cshtml.cs

On line 71 I see IsExternalLoginOnly but there seems to be NO way to get to this! The function CheckSelfRegistrationAsync returns TRUE if ANY external login exists (line 206) which would obviously make it empossible for line 71 to EVER run and thus for OnPostExternalLogin to ever run. Am I missing something? I disabled both Abp.Account.EnableLocalLogin and Abp.Account.IsSelfRegistrationEnabled but then was surprised to still see a registration screen. What am I missing? I see your response to https://support.abp.io/QA/Questions/6843/External-Provider-login-is-able-to-register-a-user-even-if-self-register-setting-is-disabled but I still think there might be a bug here? Shouldn't line 71 be able to run somehow? Shouldn't there just be a standard place to autoregister a user.

This used to be done easily by a function CreateExternalUserAsync(ExternalLoginInfo info) on LoginModel but that seemed to go away. What is the replacement to that function?

Also, previously I had made the decision to use email address for username for all users but I see this is NOT the default approach ABP takes. Is there a "standard" way to change this? Is overriding UserManager.GetUserNameFromEmailAsync() to just return the email address a bad idea?

Thanks,

Jonathan

It looks like there is a bug in "abp new" for 8.1.1 with the basic theme

• ABP Framework version: v8.1.1
• UI Type:Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yno
• Steps to reproduce the issue:

Run the following: abp new TestMe.MainApp -u blazor-server -csf --version 8.1.1 --theme basic -t app-pro

Gives These Errors:

C:\Users\xxxxxx\source\repos_build\TestMe.MainApp\src\TestMe.MainApp.Blazor\Pages_Host.cshtml(4,42): error CS0234: T he type or namespace name 'Basic' does not exist in the namespace 'Volo.Abp.AspNetCore.Components.Web' (are you missing an assembly reference?) [C:\Users\xxxxxx\source\repos_build\TestMe.MainApp\src\TestMe.MainApp.Blazor\TestMe.MainApp. Blazor.csproj] C:\Users\xxxxxx\source\repos_build\TestMe.MainApp\src\TestMe.MainApp.Blazor\MainAppBlazorModule.cs(70,12): error CS02 46: The type or namespace name 'AbpAspNetCoreMvcUiBasicThemeModule' could not be found (are you missing a using directi ve or an assembly reference?) [C:\Users\xxxxxx\source\repos_build\TestMe.MainApp\src\TestMe.MainApp.Blazor\TestMe.Mai nApp.Blazor.csproj] 0 Warning(s) 2 Error(s)

The template also seems to be using <HeadOutlet> when it should be using this in order to support the MVC pages such as the login page, right?

<component type="typeof(HeadOutlet)" render-mode="Server" />