Activities of "antonis"

Hi,

I have the following code

Client newClient = await clientRepository.InsertAsync(clientInput);

return ObjectMapper.Map<ClientDto>(newClient);

I am trying to return the new id back to the client. But apparently the Id of the newClient is a huge number -9223372036854775000 which means that the row was inserted but for some reason the Id was not set in the Client object.

How can I overcome this issue?

Hi,

My solution has different modules. apart from aspnetzero dlls I created custom modules. The same stands for angular. I created lazy loaded modules that each one does not depend on it and each module is part of license paid by client. Depending on the modules the clients is paying for I want to deploy only on:

1. asp.net core - dlls that he paid for
2. angular - only provide build that will exclude modules he did not paid for.

How can this be done with aspnet zero?

I have the same problem. Any fix?

Thanks

Since nobody is replying to github issue I am writing here for a major problem I have when I update to v7.0. I am using aspnet core with angular.

. I updated the aspnet core but I dont see my custom module appservices in the service.proxies.ts after I ran refresh.bat nor into the swagger ui. It seems that the appservices are not registered in router. I managed to get all routes of my solution. Not one route of the custom modules is present. What is the problem here? After upgrading to 7.0 this problem started happening

Thanks in advance

If it is a transient how it is caching then since every request has its own PersonCache?

Hi,

EntityCache is a singleton class. I saw the code of abp and noticed that a IRepository is injected into EntityCache. Since entitycache is singleton and dependency is scoped these would lead to captive dependency and even worse the same repository instance will be used by whatever other service is registered as singleton and uses that repository. Eventually this would cause bigger problems since dbcontext is not thread safe.

Can you advise?

Thanks

Where can I call it?

The instance will be created the first time someone requests it, and subsequently reused every time it's needed Take as example the EntityCache which is a singleton. It is using the dbcontext to get the entity from database if I am not mistaked. The first request that comes in the controller that uses an EntityCache is gonna use the dbcontext that was created for the first request. Is that right?

@mailming I understand how DI works. What I am asking how are they being initialized in abp?