To update your version to v4.3.x for both ABP CLI and ABP Suite run the following command
dotnet tool update -g Volo.Abp.Cli --version 4.3.0-rc.1
abp suite update --preview
or
Run this PowerShell script to update both the CLI and Suite to the latest including the preview versions.
v4.3 Preview ABP Framework Version Notes https://blog.abp.io/abp/ABP-Framework-4.3-RC-Has-Been-Published
v4.3 Preview ABP Commercial Version Notes https://blog.abp.io/abp/ABP-Commercial-4.3-RC-Has-Been-Published
From 4.x to 4.3 Migration Guide https://docs.abp.io/en/commercial/4.3/migration-guides/v4_3
188 Answer(s)
-
0
ABP Framework version: v4.3.0
UI type: Angular
DB provider: EF CoreProblem : wrong generate localization
@arifharsono that issue will be fixed in 4.3.1
@alper: I think it's better if we can modify the template files. BTW, when will the 4.3.1 release?
-
0
Hello Alper,
Sorry to come back with this but we still couldn't create a new tenant and use them because the user is not created. There are several of us in this situation since switching to 4.3 and this is a major problem for us because we can no longer have a new customer ...
I tested that on a new 4.3 project the problem does not appear, yet we did the migration well (via file comparison) but impossible to have a user on the creation of a new tenant.
The situation is becoming critical for us. Thank you in advance for your precious help.
Nicolas.
-
0
Hi Yes Nicholas is right, I and another also raised this, bug. I feel like this system is not the best for tracking bugs.
My post: Create new tenant not creating admin user
ABP Framework version: v4.3.0 (Upgraded from 4.2.1) UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: No error is thrown. Steps to reproduce the issue: Goto SaaS-->Tenants-->New Tenant Create a new tenant with the admin user and pass entered. Save It looks like the tenant is created but the admin user is not added. In the database the tenant is added but there is no user. Potentially a problem in ObjectExtensions or TenantAppService?
-
0
Greetings;
I am going through the Bookstore tutorial with a fresh download of Abp.io 4.3 Angular EF
After adding the entity Book, as per the directions I am setting the Default project to src<MyAppName>.EntityFrameworkCore.DbMigrations
running the command: Add-Migration "MyMigrationName"
I receive the following error:
More than one DbContext was found. Specific which one to use. Use the '-Context' parameter for PowerShell commands and the '--context' parameter for dotnet commands.
I think in your latest release documentation you state you have dynamic dbContext options now... Would this have anything to do with this?
Please advise,
--Dave
-
0
Create new tenant not creating admin user
- ABP Framework version: v4.3.0 (Upgraded from 4.2.1)
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace: No error is thrown.
- Steps to reproduce the issue:
- Goto SaaS-->Tenants-->New Tenant
- Create a new tenant with the admin user and pass entered.
- Save
It looks like the tenant is created but the admin user is not added.
In the database the tenant is added but there is no user.
Potentially a problem in ObjectExtensions or TenantAppService?Chris
I have the same problem here, ABP Framework version:* v4.3.0 from new Template.
at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter
1.InterceptAsync[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Saas.Tenants.TenantStore.GetCacheItemAsync(Nullable`1 id, String name) at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) <<<---- Error@arifharsono
the stack trace show that it doesn't find the tenant. did you clean your browser cookies? sometimes old cookies from other databases may break the new project.
-
0
Greetings;
I am going through the Bookstore tutorial with a fresh download of Abp.io 4.3 Angular EF
After adding the entity Book, as per the directions I am setting the Default project to src<MyAppName>.EntityFrameworkCore.DbMigrations
running the command: Add-Migration "MyMigrationName"
I receive the following error:
More than one DbContext was found. Specific which one to use. Use the '-Context' parameter for PowerShell commands and the '--context' parameter for dotnet commands.
I think in your latest release documentation you state you have dynamic dbContext options now... Would this have anything to do with this?
Please advise,
--Dave
hi the samples are being updated. you can set the context with the -Context parameter
-
0
Hello Alper,
Sorry to come back with this but we still couldn't create a new tenant and use them because the user is not created. There are several of us in this situation since switching to 4.3 and this is a major problem for us because we can no longer have a new customer ...
I tested that on a new 4.3 project the problem does not appear, yet we did the migration well (via file comparison) but impossible to have a user on the creation of a new tenant.
The situation is becoming critical for us. Thank you in advance for your precious help.
Nicolas.
@Nicolas,
I created a new issue about this, can you please write all the findings you have into this issue (exception logs) https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
-
0
Greetings;
I am going through the Bookstore tutorial with a fresh download of Abp.io 4.3 Angular EF
After adding the entity Book, as per the directions I am setting the Default project to src<MyAppName>.EntityFrameworkCore.DbMigrations
running the command: Add-Migration "MyMigrationName"
I receive the following error:
More than one DbContext was found. Specific which one to use. Use the '-Context' parameter for PowerShell commands and the '--context' parameter for dotnet commands.
I think in your latest release documentation you state you have dynamic dbContext options now... Would this have anything to do with this?
Please advise,
--Dave
hi the samples are being updated. you can set the context with the -Context parameter
I was able to fix the issue using the following commands: PM>Add-Migration "MyMigrationName" -context MyAppNameMigrationsDbContext PM>update-database -context MyAppNameMigrationsDbContext
Thank you.
-
0
Blazor 4.3 preview
unable to generate, is it backend template name is wrong spelling "o" and "e" ?
@Leaf, this is fixed in the patch version wait for 2021-05-21
-
0
Hello,
I think i'm the 4 person to report this :
With UI MVC EF Core and no tiered when we create a new tenant the user is not deployed (We cannot login in tenant and use it) We can't on boarding new customer in production :(
It's is ok with a new project. I have followed the migration steps for our project. (with compare method) but the problem is still there.
Thanks for your help.
erreur log is to long to post... timeout in :
at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) at Jureez.Data.JureezTenantDatabaseMigrationHandler.MigrateAndSeedForTenantAsync(Guid tenantId, String adminEmail, String adminPassword) in C:\Personnel\Developpement\Jureez\aspnet-core\src\Jureez.Domain\Data\JureezTenantDatabaseMigrationHandler.cs:line 92@Nicolas did you clean your browser cache (cookies)?
-
0
reported by @chris.tune@gmail.com
Create new tenant not creating admin user
- ABP Framework version: v4.3.0 (Upgraded from 4.2.1)
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace: No error is thrown.
- Steps to reproduce the issue:
- Goto SaaS-->Tenants-->New Tenant
- Create a new tenant with the admin user and pass entered.
- Save
It looks like the tenant is created but the admin user is not added.
In the database the tenant is added but there is no user.
Potentially a problem in ObjectExtensions or TenantAppService?Chris
The issue is more pervasive than Chris reported. None of the identity components are created for the new tenant. This includes the admin user, the default admin role and the initial permission grants needed for the new admin role.
Is there a status available for this issue? Will it be addressed in the next patch?
@scott7106 track the following link https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
-
0
For those migrated from 4.2.X to 4.3.X, you need to implement this: https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
-
0
4.3.1 abp suite dosen't work. when add new field to exist entity...
-
0
4.3.1 abp suite dosen't work. when add new field to exist entity...
@alper It tries to re-create the entity every time I add a new property. Why is this not fixed?
-
0
Volo.Forms
IQuestionAppService should implement IApplicationService
-
0
hi @gaoyao
I will handle this. Thanks
-
0
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
-
0
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
-
0
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
@Albert - Thanks for the date on v4.3.2, where can we see what will be fixed/released in the Commercial version?
Github only shows what is in the open source version.
-
0
How come that these tabs are not accessible anymore?
I discovered now I cannot access them with my admin user:
-
0
I updated all the packages in easy crm sample app (razor pages) to 4.3.2 when i ran the up, below error happened.
An unhandled exception occurred while processing the request. TypeLoadException: Method 'get_CoreOptions' in type 'Microsoft.EntityFrameworkCore.Internal.RelationalDatabaseFacadeDependencies' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=5.0.6.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkRelationalServicesBuilder.TryAddCoreServices()
DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(Microsoft.EntityFrameworkCore.DbContextOptions`1[Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext])' on type 'LanguageManagementDbContext'. Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate()
DependencyResolutionException: An exception was thrown while activating Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action
Stack Query Cookies Headers Routing TypeLoadException: Method 'get_CoreOptions' in type 'Microsoft.EntityFrameworkCore.Internal.RelationalDatabaseFacadeDependencies' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=5.0.6.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkRelationalServicesBuilder.TryAddCoreServices() Microsoft.Extensions.DependencyInjection.SqliteServiceCollectionExtensions.AddEntityFrameworkSqlite(IServiceCollection serviceCollection) Microsoft.EntityFrameworkCore.Sqlite.Infrastructure.Internal.SqliteOptionsExtension.ApplyServices(IServiceCollection services) Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.ApplyServices(IDbContextOptions options, ServiceCollection services) Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache+<>c__DisplayClass4_0.
Show raw exception details DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(Microsoft.EntityFrameworkCore.DbContextOptions`1[Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext])' on type 'LanguageManagementDbContext'. Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate() Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable<Parameter> parameters) Autofac.Core.Activators.Reflection.ReflectionActivator.<ConfigurePipeline>b__11_0(ResolveRequestContext ctxt, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Builder.RegistrationBuilder<TLimit, TActivatorData, TRegistrationStyle>+<>c__DisplayClass41_0.<PropertiesAutowired>b__0(ResolveRequestContext ctxt, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next)
Show raw exception details DependencyResolutionException: An exception was thrown while activating Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.SharingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.CircularDependencyDetectorMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, ResolveRequest request) Autofac.Core.Resolving.ResolveOperation.ExecuteOperation(ResolveRequest request) Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable<Parameter> parameters, out object instance) Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable<Parameter> parameters) Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService<T>(IServiceProvider provider) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.CreateDbContextAsync(IUnitOfWork unitOfWork) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.CreateDbContextAsync(IUnitOfWork unitOfWork, string connectionStringName, string connectionString) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.GetDbContextAsync() Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository<TDbContext, TEntity>.GetDbSetAsync() Volo.Abp.LanguageManagement.EntityFrameworkCore.EfCoreLanguageRepository.GetListByIsEnabledAsync(bool isEnabled, CancellationToken cancellationToken) Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous<TResult>(IInvocation invocation, IInvocationProceedInfo proceedInfo) Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapterWithReturnValue<TResult>.ProceedAsync() Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter<TInterceptor>.InterceptAsync<TResult>(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func<IInvocation, IInvocationProceedInfo, Task<TResult>> proceed) Volo.Abp.LanguageManagement.DatabaseLanguageProvider.c5CidUwIv() Volo.Abp.Caching.DistributedCache<TCacheItem, TCacheKey>.GetOrAddAsync(TCacheKey key, Func<Task<TCacheItem>> factory, Func<DistributedCacheEntryOptions> optionsFactory, Nullable<bool> hideErrors, bool considerUow, CancellationToken token) Volo.Abp.LanguageManagement.DatabaseLanguageProvider.GetLanguagesAsync() Microsoft.AspNetCore.RequestLocalization.DefaultAbpRequestLocalizationOptionsProvider.GetLocalizationOptionsAsync() Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Volo.Abp.AspNetCore.MultiTenancy.MultiTenancyMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Builder.ApplicationBuilderAbpJwtTokenMiddlewareExtension+<>c__DisplayClass0_0+<<UseJwtTokenMiddleware>b__0>d.MoveNext() Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) Volo.EasyCrm.Web.Data.DbMigrationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in DbMigrationMiddleware.cs + await next(context); Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
Show raw exception details
-
0
I updated all the packages in easy crm sample app (razor pages) to 4.3.2 when i ran the up, below error happened.
An unhandled exception occurred while processing the request. TypeLoadException: Method 'get_CoreOptions' in type 'Microsoft.EntityFrameworkCore.Internal.RelationalDatabaseFacadeDependencies' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=5.0.6.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkRelationalServicesBuilder.TryAddCoreServices()
DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(Microsoft.EntityFrameworkCore.DbContextOptions`1[Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext])' on type 'LanguageManagementDbContext'. Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate()
DependencyResolutionException: An exception was thrown while activating Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action
Stack Query Cookies Headers Routing TypeLoadException: Method 'get_CoreOptions' in type 'Microsoft.EntityFrameworkCore.Internal.RelationalDatabaseFacadeDependencies' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=5.0.6.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkRelationalServicesBuilder.TryAddCoreServices() Microsoft.Extensions.DependencyInjection.SqliteServiceCollectionExtensions.AddEntityFrameworkSqlite(IServiceCollection serviceCollection) Microsoft.EntityFrameworkCore.Sqlite.Infrastructure.Internal.SqliteOptionsExtension.ApplyServices(IServiceCollection services) Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.ApplyServices(IDbContextOptions options, ServiceCollection services) Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache+<>c__DisplayClass4_0.
Show raw exception details DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(Microsoft.EntityFrameworkCore.DbContextOptions`1[Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext])' on type 'LanguageManagementDbContext'. Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate() Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable<Parameter> parameters) Autofac.Core.Activators.Reflection.ReflectionActivator.<ConfigurePipeline>b__11_0(ResolveRequestContext ctxt, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Builder.RegistrationBuilder<TLimit, TActivatorData, TRegistrationStyle>+<>c__DisplayClass41_0.<PropertiesAutowired>b__0(ResolveRequestContext ctxt, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next)
Show raw exception details DependencyResolutionException: An exception was thrown while activating Volo.Abp.LanguageManagement.EntityFrameworkCore.LanguageManagementDbContext. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.SharingMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.Middleware.CircularDependencyDetectorMiddleware.Execute(ResolveRequestContext context, Action<ResolveRequestContext> next) Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, ResolveRequest request) Autofac.Core.Resolving.ResolveOperation.ExecuteOperation(ResolveRequest request) Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable<Parameter> parameters, out object instance) Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable<Parameter> parameters) Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService<T>(IServiceProvider provider) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.CreateDbContextAsync(IUnitOfWork unitOfWork) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.CreateDbContextAsync(IUnitOfWork unitOfWork, string connectionStringName, string connectionString) Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider<TDbContext>.GetDbContextAsync() Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository<TDbContext, TEntity>.GetDbSetAsync() Volo.Abp.LanguageManagement.EntityFrameworkCore.EfCoreLanguageRepository.GetListByIsEnabledAsync(bool isEnabled, CancellationToken cancellationToken) Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous<TResult>(IInvocation invocation, IInvocationProceedInfo proceedInfo) Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapterWithReturnValue<TResult>.ProceedAsync() Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter<TInterceptor>.InterceptAsync<TResult>(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func<IInvocation, IInvocationProceedInfo, Task<TResult>> proceed) Volo.Abp.LanguageManagement.DatabaseLanguageProvider.c5CidUwIv() Volo.Abp.Caching.DistributedCache<TCacheItem, TCacheKey>.GetOrAddAsync(TCacheKey key, Func<Task<TCacheItem>> factory, Func<DistributedCacheEntryOptions> optionsFactory, Nullable<bool> hideErrors, bool considerUow, CancellationToken token) Volo.Abp.LanguageManagement.DatabaseLanguageProvider.GetLanguagesAsync() Microsoft.AspNetCore.RequestLocalization.DefaultAbpRequestLocalizationOptionsProvider.GetLocalizationOptionsAsync() Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Volo.Abp.AspNetCore.MultiTenancy.MultiTenancyMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Builder.ApplicationBuilderAbpJwtTokenMiddlewareExtension+<>c__DisplayClass0_0+<<UseJwtTokenMiddleware>b__0>d.MoveNext() Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) Volo.EasyCrm.Web.Data.DbMigrationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in DbMigrationMiddleware.cs + await next(context); Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
Show raw exception details
did you try deleting bin obj folders. this usually happens when the old DLLs remain in the Bin folder.
-
0
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
@Albert - Thanks for the date on v4.3.2, where can we see what will be fixed/released in the Commercial version?
Github only shows what is in the open source version.
Andrew all the reported issues are fixed. But I'll write a list of fixed issues in this week
-
0
How come that these tabs are not accessible anymore?
I discovered now I cannot access them with my admin user:
@alexander.nikonov,
I checked it but I couldn't see any logic to disable these tabs. The marked tabs are bootstrap dropdown toggles. Maybe this is not working in your browser. Can you try it on a different browser and send me the results?
-
1
Earlier versions suite was generating AppService names singular. With version 4.3 we realised suite started to generate new service names plural.
Sample: Old:
ProductAppServiceNew:ProductsAppService
