<cite>michelmk2: </cite> That depends, what kind of reports are you talking about? We often use SSRS for all kinds of reports (Invoices, documents, some simple graphs, etc.)!
Hi, you want to try out: <a class="postlink" href="https://jsreport.net/">https://jsreport.net/</a>
Thanks, /Tommy
<cite>aaron: </cite> Domain service methods are not conventional unit of work methods.
Alternatively, you can use [UnitOfWork] attribute for:
- All public or public virtual methods for classes those are used over interface (Like an application service used over service interface).
- All public virtual methods for self injected classes (Like MVC Controllers and Web API Controllers).
- All protected virtual methods.
Hi Aaron,
Based on the link you provided.... it states the below:
"You can inject and use IUnitOfWorkManager as shown here (Some base classes have already UnitOfWorkManager injected by default: MVC Controllers, application services, <span style="color:#FF0000">domain services</span>...). Thus, you can create more limited scope unit of works. In this approach, you should call Complete method manually. If you don't call, transaction is rolled back and changes are not saved."
I interpret it as Domain Services is injected with UoW by default. Thank you for further clarification.
/Tommy
<cite>aaron: </cite> Begin a UnitOfWork:
using (var uow = UnitOfWorkManager.Begin()) { var users = _userManager.Users.ToList(); uow.Complete(); }
Hi Aaron,
Could you explain why an explicit UoW is required?
Thanks. /Tommy
<cite>alper: </cite> Write all your logic to Application Service. Whenever you need to use the same logic in different places like in different application services you should you a domain service to share the code.
Hi Alper,
Write all your logic to Application Service. Whenever you need to use the same logic in different places like in different application services you should you a domain service to share the code.[/quote]
Would it be a good practice to write the logics as Private functions within the Application Service, while keeping the actual AppService functions focusing on DTOs operations. Later stage, the same logics to be shared with other AppService, then a these Private functions can be easily ported to Domain Service.
Personally, I prefer to have logics implemented at Domain layer; however, it is extra overhead if logics are only used by a single AppService.
Are my perspectives above correct?
Thanks. /Tommy
<cite>aaron: </cite> Hi Tommy, can you try Abp.EntityFramework v2.3.0?
Hi aaron,
Able to update now.
What should I do in order to get the exception? Follow the stackoverflow approach?
Thanks. /Tommy
<cite>aaron: </cite> You need Abp.EntityFramework v2.3.0, which should be compatible with ASP.NET Zero v4.0 to v4.4. ASP.NET Zero v4.5 to v4.6 should use Abp.EntityFramework v3.1.2.
Hi aaron,
Which version should I upgrade to if I'm using MVC5AJ1? Because I'm not able to upgrade to the latest version, which is version 3.2.3 due to my .NETFramework is 4.6.1
Thanks. /Tommy
<cite>ismcagdas: </cite> Thanks for sharing it here @tteoh :)
You're welcome :D
Thanks. /Tommy
<cite>ismcagdas: </cite> Hi @tteoh,
Can you explain how do you prevent multiple logins ? We can suggest somnething accordingly.
Thanks.
Hi @ismcagdas,
This: [https://forum.aspnetboilerplate.com/viewtopic.php?f=5&t=6729&p=22492#p22492])
Thanks. /Tommy
This problem is fixed. Please go to the link below to check how is it being fixed.
[https://github.com/aspnetboilerplate/module-zero/issues/413])
Hope this might help those people who is trying to do prevent multiple login as well. Feel free to ask me if you have any problem and I will try my best to help.
Thanks. /Tommy
Hi,
I'm doing prevent multiple login and it's working fine now. But I've a question about it, which is can I prevent the multiple login no matter it's from browser or other agents (such as Postman)?
Thanks. /Tommy