Current filter:
                                You should refresh the page.
                                  • How much will that affect me?
                                    Technically, several interfaces, classes and enumerations were moved to the DevExpress.Persistent.Base and DevExpress.Persistent.BaseImpl libraries from the following assemblies:
                                        DevExpress.ExpressApp.Charts
                                        DevExpress.ExpressApp.Kpi
                                        DevExpress.ExpressApp.ConditionalAppearance
                                        DevExpress.ExpressApp.StateMachine
                                    Note that we intentionally do not explicitly list all these types here as they did not change their namespaces.
                                    Your application will continue working as previously if you ensure the DevExpress.Persistent.Base (for both Entity Framework (EF) and eXpress Persistent Objects (XPO) data access options) and DevExpress.Persistent.BaseImpl (XPO only) assemblies are referenced in the XAF application projects where these four modules were referenced. This is usually done by default so this change should not affect you in 99.99% of cases unless you are building a complex framework that relies on the location of these types.

                                    Why was this change done?
                                    The DevExpress.Persistent.Base library usually contains ORM-agnostic base business classes and interfaces that can operate for both EF and XPO ORM libraries, while the DevExpress.Persistent.BaseImpl.EF and DevExpress.Persistent.BaseImpl libraries are supposed to hold ORM-based example implementations of these base interfaces for EF and XPO respectively.  You can learn more on this from the eXpressApp Framework > Concepts > Business Model Design > Built-in Business Classes for Most Popular Scenarios  documentation.
                                    This change was required for easier maintenance and extension of our extra modules code + for further clearance from indirect XPO dependencies, which existed previously.

                                • Simon Roy 08.15.2016

                                  Hi Dennis,

                                  We're using extensively XpoStateMachine and XpoTransition, and previously we chose not to include DevExpress.Persistent.BaseImpl as we have our own implementations for Country, and Task among others.

                                  Even if the namespaces did not change, we are now obligated to include DevExpress.Persistent.BaseImpl in our solution.

                                  This causes all base or demo objects from DevExpress to be included in our application. Would it be possible to separate the base objects from the rest of the library?

                                • Michael (DevExpress Support) 08.16.2016

                                  @Simon: Despite the fact that the DevExpress.Persistent.BaseImpl library contains various business objects, they are not included in the XAF application model by default. These classes (if required) need to be added explicitly as described in the Add a Class from the Business Class Library (XPO) article. So, adding a reference to the DevExpress.Persistent.BaseImpl library shouldn't break anything. If you faced an issue after adding the library to your project, please submit a new ticket and describe the issue in detail.

                                0 Solutions

                                Creation Date Importance Sort by