orchard core دیگر یک وب سایت مدیریت محتوا نیست !
در نسخه Core این پروژه ( که به صورت کامل باز طراحی و بازنویسی شده ) تبدیل به یک سایت ساز شده است .
It is a completely new thing written in ASP.NET Core. The Orchard CMS was designed as a CMS, but Orchard Core was designed to be an<< application framework >> that can be used to build a CMS, a blog or whatever you want to build
ممنون از را حلی که ارائه دادین، اشکال مربوطه رفع شد... مهندس جان حین اجرای برنامه و بدون استفاده از StructureMap حین اجرای برنامه کانکشن استرینگ رو تغییر میدم و از دیتابیسی به دیتابیس دیگه ای میرم و با تغییر متغییر و پارامتر مورد نظر کاملا جواب میده ولی وقتی با استفاده از StructureMap و روشی که فرمودین عمل میکنم اجازه سوئیچ روی دیتابیس دیگه رو نمی‌ده وتغییری هم درکانکشن استرینگ جدید ارسال شده به Context مربوطه مشاهده نمی‌شه . کاربر حتما نیاز به تغییر سال عملیاتی حین اجرای برنامه و یا دسترسی به اطلاعات سال عملیاتی همتا رو بدون خروج از سال عملیاتی جاری داره....
این error رو میده :
The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext might be in an inconsistent state. Inner exception message: A referential integrity constraint violation occurred: The property values that define the referential constraints are not consistent between principal and dependent objects in the relationship.
...
Tuple does many things KeyValuePair does not. Tuples are comparable, they implement the IComparable and IStructuralEquatable interfaces, so it makes compare two tuple
...
Vertical Slice Architecture, not Layers!
Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change.
This architecture and styleguide has been rewritten from the ground up for ES2015, the changes in Angular 1.5+ for future-upgrading your application to Angular 2.
