Ends in:
5 DAYS
17 HRS
10 MIN
48 SEC
Ends in:
5 D
17 H
10 M
48 S

Activities of "kirtik"

Getting this error when i run Add.migration command in console.

But the dbcontext exists here.....

Yes. That worked !! Thanks

No it is not resolved. I have already referenced -- using Volo.Abp.Domain.Entities;

@maliming Thanks for the solution.

How do i resolve this error ?

@maliming Shared the project with you

sure . will share now.Thanks.

I am performing a proof of concept for using Azure Cosmos DB. I am following these steps to use Azure Cosmos DB from mvc/jquery ABP.IO application. https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Other-DBMS I am at the last step of "Re-Generate the Migrations". However i started getting exceptions for many tables for the concurrencyStamp property which i resolved one by one by using the IsETagConcurrency() and it worked for all entities so far. But its not working for the <ApiResource> entity.

I tried ignoring the entity but still getting the same error. Its not ignored at all. Maybe since its defined in the matadata ?

<br> Could you please help me since i think my Azure Cosmos will work if this issue is resolved.

I am already running Swagger . I run API.Host first (Ctrl + F5) and then the Blazor Project (Ctrl + F5)

  • ABP Framework version: v4.0.0
  • UI type: Blazor
  • Tiered (MVC) or Identity Server Seperated (Angular): no

I have tried to run the Blazor project in three different variations today. However with each project the swagger runs without problem but when the Blazor project is run i get all these errors in console.

I have not made any changes in code at all. Just running the plain vanilla application.

Also tried to run the BookStore-Blazor-EfCore and EventOrganizer from samples master, but same errors.

Am i missing some package ? Can you please provide pointers ?

Thanks

Showing 21 to 30 of 50 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 26, 2024, 12:49