Activities of "a3x"

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

You describe the new database migration system here: https://blog.abp.io/abp/ABP.IO-Platform-7-4-RC-Has-Been-Published I like to auto migrate my application on startup, however, the description is not total clear for me. Can you please bring an example how to implement it in a normal MVC application?

• ABP Framework version:7.3.2
• UI Type: MVC /
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no

When running the "Update all ABP packages" I see that you install jquery from a version of 2018. This versions have a lot of known vulnerabilities. Could you please ensure that the latest javascript frontends are used?

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v7.0.0

I updated to abp v7.0.0. I can run my application, however, when running the unit tests I receive following errors randomly for the tests.

Message:  Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module TestProjectDb.TestProjectDbTestBaseModule, TestProjectDb.TestBase, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: SqliteConnection does not support nested transactions.. See the inner exception for details. ---- System.InvalidOperationException : SqliteConnection does not support nested transactions.

Stack Trace:  ModuleManager.InitializeModules(ApplicationInitializationContext context) AbpApplicationBase.InitializeModules() AbpApplicationWithExternalServiceProvider.Initialize(IServiceProvider serviceProvider) AbpIntegratedTest1.ctor() TestProjectDbTestBase1.ctor() TestProjectDbApplicationTestBase.ctor()

I found https://support.abp.io/QA/Questions/2176/Regarding-Unit-test-issue and replaced the service as described, however, this does not fix my problem. I do understand the problem but dont know how to fix this or what changed between my last v6.0.0 and this version?

• ABP Framework version: vX.X.X
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

Hello,

in our company we run all projects through the well-known tool snyk.io to find vulnerabilities. Thereby we noticed some vulnerabilities, which come into the project through abp.io. To fix them we think it is important that you update the abp.io packages and provide a new version. Since abp.io is already used by many companies it would be good if you regularly use synk or a similar tool yourself and update the dependencies within your abp.io modules.

In the attachment some examples:

• ABP Framework version: v6.0.0
• UI type: MVC
• DB provider: EF Core /
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:

Autofac.Core.Registration.ComponentNotRegisteredException The requested service 'Volo.Abp.IdentityServer.Tokens.TokenCleanupBackgroundWorker' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.

After upgrading to v6.0.0 and migrating to OpenIddict I receive following error. The cause seems to be clear: Since the service was removed it cannot be executed. However, what needs to be done in order to migrate the hangfire job?

• ABP Framework version: v5.3.4
• UI type: MVCr
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:

In a project I set the attribute <Nullable>enable</Nullable> within all my projects (csproj) in order to allow nullable types.

After starting the application I get for all tables and fields the error message "Field XXX is required" However, the fields are not marked as required in the view, nor in any DTO.

How can I solve this one?

Hi,

we are using snyk to automaticaly scan our repo for vulnerable Dependencies. We noticed that the latest theme version comes with outdated and vulnerable libraries

Sine this will affect all our clients it would be great if you update all libraries and also include scanners like snyk to your software development lifecycle.