Activities of "viswajwalith"

• ABP Framework version: v5.1.3
• UI type: MVC
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): es / Microservice
• Exception message and stack trace:
• Steps to reproduce the issue:"

We upgraded our application from 4.4.0 to 5.1.3. we could not find volo.abp.identity Do we missing any references that need to be added in v5.1.3

Added references to HttpApi layer of the microservice in Web. Now it is generating Dynamic Proxies.

• ABP Framework version: v5.1.3
• UI type: MVC
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / Microservice
• Exception message and stack trace:
• Steps to reproduce the issue:"

We upgraded our application from 4.4.0 to 5.1.3. we are facing error with Redis.

Include="Microsoft.AspNetCore.DataProtection.StackExchangeRedis" Version="6.0.0" Include="Volo.Abp.Caching.StackExchangeRedis" Version="5.1.3"

Already there are microservice HttpApi reference in web gateway like product service. if we give web gateway reference in HttpApi layer of the microservice, there will be circular dependency. Dynamic proxies generating for product service with existing references but not for our other microservices.

• ABP Framework version: v5.1.3
• UI type: MVC
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / Microservice
• Exception message and stack trace:
• Steps to reproduce the issue:"

We upgraded our application from 4.4.0 to 5.1.3

Product Service is generating dynamic proxies in 5.1.3, our Employee Service is not generating dynamic proxies in 5.1.3 In 4.4.0 our Employee Service was able to generate dynamic proxies successfully.

hi

https://blog.abp.io/abp/ABP.IO-Platform-v5-1-Has-Been-Released

If we understand correctly, Lepton X is not yet part for ABP 5.1 for MVC version. Please let us know

• ABP Framework version: v5.1
• UI type: MVC
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

We just tried the Latest 5.1 ABP.IO version but didn't got the LeptonX , are we missing anything here or LeptonX is not part of ABP.IO solution yet.

Yes It worked, I think this is an issue at your end and we expect a refund of ticket

• ABP Framework version: v4.3
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / no
• Exception message and stack trace:
• Steps to reproduce the issue:"

We are unable to login to CLI, it seems some issue at your end can you please guide us.

FYI... we have a valid license till 2023

Hi,

We tried to implement the Azure AD B2C, everything this working fine, if we use same configuration for all tenants.

When we try to implement tenant based configuration, ClientId and ClientSecret are taking as per the tenant configuration, but Authority is not taking as per the tenant configuration.