Activities of "EngincanV"

Hi, it seems an error occurs when Suite tries to generate proxies (for only ms solution, as far as I see). I'm able to reproduce the problem and will fix it asap. Btw, I have refunded your ticket.

Best regards.

May I have a status update on this please?

Hi, I could successfully reproduce the error with your entity metadata. I have created an internal issue for it and will fix it asap. You can manually update the method name on the UI side for a quick workaround.

Regards.

Have you looked into this?

Hi, I have tried just before but unfortunately, I'm unable to reproduce it, due to missing parts (enum files etc...). If it's possible can you share the full application via email with us, so we can better assist you?

Hi, it seems an error occurs when Suite tries to generate proxies (for only ms solution, as far as I see). I'm able to reproduce the problem and will fix it asap. Btw, I have refunded your ticket.

Best regards.

Hi, thanks for reporting this problem. We successfully identified the problem and will fix it asap. In the meantime, you can add the related CMS Kit Pro package to the Blazor.Client project as well. Btw, I have refunded your ticket.

Regards.

Hi, Thank you for identifying the problem and issuing the refund. I appreciate your prompt response.

I need a bit more clarification regarding the suggested workaround. When you mentioned adding the related CMS Kit Pro package to the Blazor.Client project, which package should I add to get CMS pro working, tried a handful of packages but none worked for me.

Thank you

Hi, sorry for the late response. You should add the Volo.CmsKit.Pro.Admin.Blazor.WebAssembly package into your *.Blazor.Client project and add the [DependsOn(typeof(CmsKitProAdminBlazorWebAssemblyModule))] statement to the top of your *.Blazor.Client project's module class.

Hi, thanks for reporting this problem. We successfully identified the problem and will fix it asap. In the meantime, you can add the related CMS Kit Pro package to the Blazor.Client project as well. Btw, I have refunded your ticket.

Regards.

Once I updated the nuGet packages to the new ABP version, my integration tests throw the following error. As you can see, I used the SampleTests as an example:

Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module MyProject.MyProjectTestBaseModule, MyProject.TestBase, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: Method not found: 'System.String Volo.Abp.Localization.LanguageInfo.get_FlagIcon()'.. See the inner exception for details. 
---- System.MissingMethodException : Method not found: 'System.String Volo.Abp.Localization.LanguageInfo.get_FlagIcon()'. 

I have adjusted the LocalizationOptions according to the migration guide and I have also created a new migration and applied it

Full stacktrace:

ModuleManager.InitializeModules(ApplicationInitializationContext context) 
AbpApplicationBase.InitializeModules() 
AbpApplicationWithExternalServiceProvider.Initialize(IServiceProvider serviceProvider) 
AbpIntegratedTest`1.ctor() 
MyProjectTestBase`1.ctor() 
MyProjectDomainTestBase`1.ctor() 
SampleDomainTests`1.ctor() Zeile 20 
EfCoreSampleDomainTests.ctor() 
RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions) 
----- Inner Stack Trace ----- 
LanguageManagementDataSeeder.SeedAsync() 
AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine) 
LanguageManagementDataSeeder.SeedAsync() 
LanguageManagementDataSeedContributor.SeedAsync(DataSeedContext context) 
DataSeeder.SeedAsync(DataSeedContext context) 
AsyncInterceptorBase.ProceedAsynchronous(IInvocation invocation, IInvocationProceedInfo proceedInfo) 
CastleAbpMethodInvocationAdapter.ProceedAsync() 
UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) 
CastleAsyncAbpInterceptorAdapter`1.InterceptAsync(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func`3 proceed) 
<<SeedTestData>b__0>d.MoveNext() Zeile 41 
--- End of stack trace from previous location --- 
TaskExtensions.WaitAndUnwrapException(Task task) 
<>c__DisplayClass15_0.<Run>b__0(Task t) 
ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) 
--- End of stack trace from previous location --- 
ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) 
Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) 
--- End of stack trace from previous location --- 
TaskExtensions.WaitAndUnwrapException(Task task) 
AsyncContext.Run(Func`1 action) 
AsyncHelper.RunSync(Func`1 action) 
MyProjectTestBaseModule.SeedTestData(ApplicationInitializationContext context) Zeile 37 
MyProjectTestBaseModule.OnApplicationInitialization(ApplicationInitializationContext context) Zeile 32 
OnApplicationInitializationModuleLifecycleContributor.Initialize(ApplicationInitializationContext context, IAbpModule module) 
ModuleManager.InitializeModules(ApplicationInitializationContext context) 

Hi, we removed the FlagIcon property in this version, please see the migration guide. You should probably have an old NuGet package version somewhere in your test application, or in one of the dependent projects. Please check package versions manually. If you could not find the reason, feel free to open a new ticket and after that share your project with us, so we can better assist you.

Hi sorry for the late response. I'll check this asap.

I will send the compressed zip file to support via email.

Thanks.

trying to upgrade by executing command abp update but it only update from v8.1.3 to v8.1.4.

For a clean installation, please follow the steps below:

• To update ABP CLI run the following commands:

dotnet tool uninstall -g Volo.Abp.Cli  
  
dotnet tool install -g Volo.Abp.Cli --version 8.2.0-rc.5  

• To update ABP Suite run the following commands:

dotnet tool uninstall -g Volo.Abp.Suite  
  
abp suite install --version 8.2.0-rc.5  

Then, to update your project, you can either update it through the ABP Suite UI or by running the command below:

abp update  

also getting below error

You should specify the version because it's a release candidate. Therefore, please try the command below:

abp update --version 8.2.0-rc.5