It's very late ... but this exception hurting myself by lot of hours!
Basically it happens when I'm trying to use a service injected by IoC... on method 'ValidateObjectRecursively'!
As said.. it's too late to share some further info ...
Someone has an idea when and how this overflow can be happen?
Thank for reply! As always, you are very helpful!
Understood Edition/feature mechanism, good clarification!
About multiple DbContext, I know and tried that ... but in my scenario modules can refer to entity of other module. Using separate DbContext whit different ContextKey make EF to "recreate" table mapped to entity in referenced assembly.
And this is not good!
I'm approaching to as system that can provide verticalized solution when needed.
For example, if I have developed a module for managing contacts, and I have two customer that can use this module, simply start from AspNetBoilerPlate template, add my own nuget package and that's all!
This maybe sound strange, but is commonly in our "customer habitat" where they want own server inside their office ... because they feel more secure.... mah... I never understand this thoughts!
So finally I'm imaging a separate ABP modules that are able to manage their own migrations, and concur to one big application-per-customer based on their needs.
<cite>@fncap on Gitter Chat: </cite> I've a question about how to organise entities on project suppose you are developing a SaaS app organised in features and editions like an e-commerce (but I don't develop an e-commerce) so you can organise editions to sell a module for managing contacts, and another editions to sell orders management so ... in first module i can have an entity called Category that refers to product category, and in orders module i can have another entity with same name but refers to Contact category the have placed an order actually I have to put in a common DbContext two IDbSet with different name, like ProductCategories and ContactsCategories.
It would be nice if i can refer to ProductCategories like a namespaces ... e.g. DbContext.Catalogue.Categories.GetAll() and refer to other entity same way, like DbContext.Orders.Categories.GetAll() someone have an idea ?
Nobody are using Gitter Chat? <a class="postlink" href="https://gitter.im/aspnetboilerplate/aspnetboilerplate">https://gitter.im/aspnetboilerplate/aspnetboilerplate</a>
Thanks for reply! When .net core will be supported, I'll be very happy!
First of all, congrats for this must-have framework.
As subject says ... is there any plan to make it available on vNext so we can use multiplatform either for developing and production?
I'd like to use vscode on my mac to develop and deploy app on IIS ;)
Hi and first of all congrats for you work on Aspnetboilerplate. It's a must-have framework for all of us.
My question is very simple: are you planning a porting to mono framework for cross-platform compatibility either for development or production?
It would be a great feature if we can coding on newly vscode and run our projects on OS X/win/*unix platform!
Have you thinking about this?
Thanks!