Ends in:
3 DAYS
8 HRS
22 MIN
7 SEC
Ends in:
3 D
8 H
22 M
7 S

Activities of "joerguth"

Ok, thank's.

Seems to me, that daterangepicker (.js;.css, etc) is missing in the package of abp suite

  • ABP Framework version: v7.1.0-rc.2
  • UI type: MauiBlazor
  • DB provider: EF Core
  • Tiered: yes
  • Exception message and stack trace: Volo.Abp.AbpInitializationException: "An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.AspNetCore.Components.MauiBlazor.AbpAspNetCoreComponentsMauiBlazorModule, Volo.Abp.AspNetCore.Components.MauiBlazor, Version=7.0.2.0, Culture=neutral, PublicKeyToken=null: An error occurred during the ABP remote HTTP request. (Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (localhost:44300)) See the inner exception for details.. See the inner exception for details." Stacktrace: bei Volo.Abp.Modularity.ModuleManager.InitializeModules(ApplicationInitializationContext context) bei Volo.Abp.AbpApplicationBase.InitializeModules() bei Volo.Abp.AbpApplicationWithExternalServiceProvider.Initialize(IServiceProvider serviceProvider) bei xxx.MauiBlazor.App.InitializeAbpApplication(IAbpApplicationWithExternalServiceProvider abpApplication, IServiceProvider serviceProvider) in D:\DEV\src\xxxxx.MauiBlazor\App.xaml.cs: Zeile21

InnerException Source Volo.Abp.Http.Client

  • Steps to reproduce the issue:"

I created a new application with the cli version 7.1.0-rc.2 and did not make any changes. abp new DemoApp -t app-pro -u maui-blazor --separate-auth-server --with-public-website --no-random-port

After running DbMigrator, the AuthServer, HttpApi.Host and MauiBlazor were started. The MauiBlazor application started but an exception occurs in App.xaml.cs => InitializeAbpApplication.

v7.1.0-rc.2 App.xaml.cs

public App(
        IAbpApplicationWithExternalServiceProvider abpApplication,
        IServiceProvider serviceProvider)
    { 
        InitializeComponent();
        InitializeAbpApplication(abpApplication, serviceProvider);
    }

private void InitializeAbpApplication(IAbpApplicationWithExternalServiceProvider abpApplication, IServiceProvider serviceProvider)
    {
        try
        {
            abpApplication.Initialize(serviceProvider);
            MainPage = new MainPage();
        }
        catch (AbpInitializationException ex)
        {
#if DEBUG
            MainPage = GetErrorPage(ex.Message);
#else
            MainPage = GetErrorPage("Application couldn't be initialized.");
#endif
        }
    }

v7.0.2 App.xaml.cs

public App()
    {
        InitializeComponent();

        MainPage = new MainPage();
    }

In the template of Version 7.0.1 there was no start problem, the Source of MauiProgram.cs includes this additional lines:

 public static MauiApp CreateMauiApp()
{
// snip    
var app = builder.Build();
app.Services.GetRequiredService<IAbpApplicationWithExternalServiceProvider>().Initialize(app.Services);
return app;
}

Hi, yes i did.

@liangshiwei meanwhile I have made the following changes: Reverted following code from template version 7.0.1, this works so far.

For what reason the template was changed?

App.xaml.cs ctor without calling InitializeAbpApplication

public App(
        IAbpApplicationWithExternalServiceProvider abpApplication,
        IServiceProvider serviceProvider)
    {
        InitializeComponent();
        // JU Workaround
         // InitializeAbpApplication(abpApplication, serviceProvider);
        MainPage = new MainPage();
    }

MauiProgram.cs

public static MauiApp CreateMauiApp()
{
 // snip
// JU Workaround
        // return builder.Build();
        var app = builder.Build();
        app.Services.GetRequiredService<IAbpApplicationWithExternalServiceProvider>().Initialize(app.Services);
        return app;
}

Maybe this can help:

private async Task<bool> IsRemoteServiceUp(IAbpApplicationWithExternalServiceProvider abpApplication) 
    {
        var configuration = abpApplication.Services.GetConfiguration();
        var remoteServiceUri = configuration["RemoteServices:Default:BaseUrl"];

        if (remoteServiceUri == null)
        { 
            return false; 
        }
        var ping = new System.Net.NetworkInformation.Ping();
        var host = new Uri(remoteServiceUri).Host;

        var reply = await ping.SendPingAsync(host);

        return reply.Status == System.Net.NetworkInformation.IPStatus.Success;
    }

Sorry for posting this Ping Example it didnt work because it only works with the host without the ports. I am seeing two ways: 1.) with new System.Net.Sockets.TcpClient(); 2 ) with AddHttpClient and using Polly with AddTransientHttpErrorPolicy and AddPolicyHandler

  • ABP Framework version: v7.2.0-rc.1
  • UI type: Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
    • Exception message and stack trace:
  • 2023-04-14 08:08:43.493 +02:00 [FTL] Host terminated unexpectedly! Volo.Abp.AbpInitializationException: An error occurred during PreConfigureServicesAsync phase of the module Volo.Abp.AspNetCore.Mvc.UI.Widgets.AbpAspNetCoreMvcUiWidgetsModule, Volo.Abp.AspNetCore.Mvc.UI.Widgets, Version=7.1.0.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details.

---> System.MissingMethodException: Method not found: 'Void Microsoft.Extensions.DependencyInjection.ServiceCollectionRegistrationActionExtensions.OnRegistred(Microsoft.Extensions.DependencyInjection.IServiceCollection, System.Action1<Volo.Abp.DependencyInjection.IOnServiceRegistredContext>)'. at Volo.Abp.AspNetCore.Mvc.UI.Widgets.AbpAspNetCoreMvcUiWidgetsModule.AutoAddWidgets(IServiceCollection services) at Volo.Abp.AspNetCore.Mvc.UI.Widgets.AbpAspNetCoreMvcUiWidgetsModule.PreConfigureServices(ServiceConfigurationContext context) at Volo.Abp.Modularity.AbpModule.PreConfigureServicesAsync(ServiceConfigurationContext context) at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() --- End of inner exception stack trace --- at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() at Volo.Abp.AbpApplicationFactory.CreateAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action1 optionsAction) at xxx.Blazor.Program.Main(String[] args) in Program.cs:line 36

  • Steps to reproduce the issue:" Good morning,

I have created a new Blazor Server tiered project with abp suite version 7.2.0-rc.1.

After running DbMigrator I started the applications Api.Host, AuthServer and Blazor.

The Blazor application throws an exeption.

I think that in the package Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX => Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared the reference to Volo.Abp.AspNetCore.Mvc.UI.Widgets (v7.1.0) cause it.

Thanks i will wait until it is available and check it out

Version="2.2.- works thanks

Showing 11 to 20 of 26 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on December 02, 2024, 12:35