Hi All
This is relating to a question I raised on Modual Project Strucutre. https://support.aspnetzero.com/QA/Questions/9272/Question-on-Structuring-Project
By default the powertools creates files in the "main projects" Is there a way to configure the Power Tools to create the code in different projects? Or at least in a place where it's easier to extract :)
e.g. If I was creating a numbre of entities/services/etc in the MYFeature it would put them in a seperate project Base.Application Base.Application.Shared Base.Core Base.Core.Shared MYFeatureModule.Application <--- CREATE HERE MYFeatureModule.Application.Shared<--- CREATE HERE MYFeatureModule....<--- CREATE HERE
Cheers Chris
Hi All
I'm in the process of planning a project using the angulat + net core and wanted to ask advice on strucuring my .net project for the best maintainability. For example when I use the power tool it adds the code into the modules, but would it be better to have seperate project modules for parts of my app, this would allow me to more easily seperate the core ABP from my app services and domain logic etc.
e.g. Base.Application Base.Application.Shared Base.Core Base.Core.Shared MYFeatureModule.Application MYFeatureModule.Application.Shared MYFeatureModule....
etc.
Are there any best practices for this any where?
Cheers Chris
Hi All
I'm trying to achieve a few of things with background jobs:
I dont want to have to build this out as it feels like I should be able to do this through the background job store etc.
Some design / code samples would be useful if possible :)
Thanks Chris
Hi All
Just wondering if the Webhook feature was in progress or when the drop date would be?
If it's not on the list I was thinking of creating my own or hacking a quick one using the notification framework and implementing a RealTime sender. Unless thats a bad idea ;)
Chris