Activities of "sridhar"

[AI-Bot] said:

• Yes. In ABP 10.x you can continue using AutoMapper in your own application/modules if you purchase/hold a valid AutoMapper commercial license.
• ABP 10 migrated ABP modules/templates to Mapperly, so modules like Text Template Management use Mapperly internally by default, but ABP still provides both AutoMapper and Mapperly integrations and they can co-exist in the same solution.
• Practical implications:
  • You can keep your existing AutoMapper Profiles and registrations for your code.
  • ABP module code will still use Mapperly where it was migrated.
  • If you use context-based registration like AddAutoMapperObjectMapper<TModule>(), make sure consumers map with the same ObjectMapperContext to avoid “No object mapping was found…” errors in some layers (e.g., Blazor).

Links:

• https://abp.io/docs/10.0/release-info/migration-guides/abp-10-0
• https://abp.io/docs/latest/release-info/migration-guides/AutoMapper-To-Mapperly
• https://abp.io/docs/latest/framework/infrastructure/object-to-object-mapping#advanced-topics

---

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

This is for "Text Template Management " assume I'm not going to use Mapperly and will continue with AutoMapper (with license) will I be able to use Text TemplateManagement?

Problem:

We recently Moved from to migrated to ABP version 10.x from 9.x and we could see most of the template parts(Volo.Abp.TextTemplateManagement.TextTemplates ,TemplateContentAppService) rely on Mapperly code in the recent version.

Question Most of those template parts are reused , In case if we buy a license for AutoMapper can we continue using AutoMapper?

ABP Framework version: v7.2.2

UI Type: Angular(Basic Theme) V15

Database System: EF Core (SQL Server)

Tiered (for MVC) or Auth Server Separated (for Angular): yes We use Azure B2C

Exception message and full stack trace:

Steps to reproduce the issue: We generated proxy using the below command

ng generate @abp/ng.schematics:proxy-add --target=XYZ --source=XYZ

But I'm getting the following errors

1. Error: src/app/proxy/volo/abp/domain/entities/models.ts:7:51 - error TS2315: Type 'Entity' is not generic.

   7 export interface BasicAggregateRoot<TKey> extends Entity<TKey> {

2. Error: src/app/proxy/volo/abp/identity/models.ts:4:40 - error TS2315: Type 'Entity' is not generic.

   4 export interface IdentityClaim extends Entity<string> { ~~~~~~~~~~~~~~

How to overcome this issue. This is an urgent issue could I get an answer for this asap.

Thanks in advance.

Even I have the same issue and when I ported the Application from ABP7.2.2 to 8.0.4. Have got no issues in the backend though.

main.ts:13 NullInjectorError: NullInjectorError: No provider for InjectionToken CORE_OPTIONS! at NullInjector.get (core.mjs:5601:27) at R3Injector.get (core.mjs:6044:33) at R3Injector.get (core.mjs:6044:33) at injectInjectorOnly (core.mjs:911:40) at Module.ɵɵinject (core.mjs:917:60) at Object._RestService_Factory [as factory] (abp-ng.core.mjs:59:84) at core.mjs:6164:43 at runInInjectorProfilerContext (core.mjs:867:9) at R3Injector.hydrate (core.mjs:6163:17) at R3Injector.get (core.mjs:6033:33)

Sorry I have a situation where I wont be able to upgrade now. Could you suggest me an alternative in 7.2.2

Ok I just put https://google.ca just as an example , actually I need to book keep the original url and redirect to this Url after successfully logged in, the issue is not about CORS ,

Issue is its not able to redirect to the original url after logging in. inspite of following the ABP way of mentioning redirectUrl. It would be great if you could guide me in those directions

I referred to these ABP link's but none of them are helping me https://github.com/abpframework/abp/issues/16588 https://support.abp.io/QA/Questions/5051/How-can-I-redirect-the-user-to-the-previous-URL-after-login

Ok I just put https://google.ca just as an example , actually I need to book keep the original url and redirect to this Url after successfully logged in, the issue is not about CORS ,

Issue is its not able to redirect to the original url after logging in. inspite of following the ABP way of mentioning redirectUrl. It would be great if you could guide me in those directions

I referred to these ABP link's but none of them are helping me https://github.com/abpframework/abp/issues/16588 https://support.abp.io/QA/Questions/5051/How-can-I-redirect-the-user-to-the-previous-URL-after-login

ABP Framework version: v7.2.2

UI Type: Angular

Database System: EF Core (SQL Server)

Tiered (for MVC) or Auth Server Separated (for Angular): yes

Exception message and full stack trace:

Steps to reproduce the issue:

We are using ABP with Angular , I have a situation in which on click of any link I want the user to be directed to login and after successful login we have to redirect the user to the same page that whatever user clicked before.

I tried this, const params = { returnUrl: 'https://www.google.ca/' }; this.authService.navigateToLogin(params);

I also tried it with my own Auth guard (canActivate) but they dont seem to be redirecting to the old url before logging in.

Please let me know what is the alternative to make this work(in Angular).

User Presses a Link => Redirect to Login Page => User again redirected to the link in step 1.