can you send your project to support@abp.io delete all bin and obj folders. and share it on google drive and send us link
normally there should be an ID field in Book entity. What's the base class of your entity? Did you delete the Id field from your Book.json
You can report the bugs & issues under this topic in the latest v2.5
Update the ABP CLI:
dotnet tool update -g Volo.Abp.Cli
Update the ABP Suite:
abp suite update
@trendline, see => https://support.abp.io/QA/Questions/89#answer-a3d1f7fe-fc49-147d-5f0e-39f46acb7d61
Most likely, there's an invalid cookie related with another project. The cookie names are same, so when you run different projects, it cannot be validated.
Other potential problem can be, the IdentityServer project is not running.
An unhandled exception occurred while processing the request. SocketException: No connection could be made because the target machine actively refused it. System.Net.Http.ConnectHelper.ConnectAsync(string host, int port, CancellationToken cancellationToken)
HttpRequestException: No connection could be made because the target machine actively refused it. System.Net.Http.ConnectHelper.ConnectAsync(string host, int port, CancellationToken cancellationToken)
IOException: IDX20804: Unable to retrieve document from: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.]'. Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(string address, CancellationToken cancel)
InvalidOperationException: IDX20803: Unable to obtain configuration from: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.]'. Microsoft.IdentityModel.Protocols.ConfigurationManager<T>.GetConfigurationAsync(CancellationToken cancel)
See this doc => https://docs.abp.io/en/abp/latest/How-To/Azure-Active-Directory-Authentication-MVC it's MVC based but I guess it'll guide you.
hi,
it doesn't support module templates for now. this feature will be added in the next releases
this feature is coming up in 2.4.1 (will be released 8 April)
there's no template for adding the DbSet to the DbContext.
Wait for v2.4.1 which I guess solves your problem (probably it'll be released today 08 April)
If it's not solved, I need to get your solution to reproduce it.