New XAF community modules
- The eXpand Framework, managed by Apostolis Bekiaris, will soon release new platform-agnostic packages for XAF: http://xaf.expandframework.com/. Unlike the former monolithic version of eXpand, these are low-dependency packages. They also work with previous XAF versions, and include unit tests that run on Azure (an example is available here), wiki and demos. This is a preview for now and there are known issues, so please stay tuned. Just to name a few modules to better understand their functionality:
- AutoCommit , CloneMemberValue, CloneModelView, MasterDetail,
- ModelViewInheritance, SuppressConfirmation, ViewEditMode. - A new version of XAFARI that works with v18.2.7 is available and the v18.2.8 build is on its way too. Galaktika Soft has been providing paid reusable XAF modules with documentation and support services for more than 5 years.
- LlamaChant published a maintenance update for their free modules, in case you missed it: http://www.llamachant.com/single-documents/llamachant-framework-modules/.
- https://github.com/SenDevGmbH/SenDevXafDashboards - this extension from Sergej Derjabkin adds 2 new data sources to the DevExpress XAF Dashboards module: C# Script Data Source and Data Extract Data Source. Sergej Derjabkin has been working with DevExpress components from 2003 and made several other contributions to the DevExpress community:
- Google MapView module for eXpand; Roslyn analyzers for XAF; MasterDetail module for eXpand; Nuget packages to host the middle-tier Application Server inside an XAF Web app. - https://github.com/egarim/Ultra - more community-based XAF modules under the Microsoft Public License from Joche Ojeda. You might know Joche from his promotion efforts in the Spanish community. These new modules have basic usage documentation and demos:
- Email Module allows you to use SMTP email accounts inside of your XAF application.
- Universal Search Module helps you search across all business objects and present a unified search result.
New XAF community blogs, tips & tricks
- https://www.xafers.jobs/ - a new web site for XAF experts to find jobs, employment and career opportunities. This may be a good alternative to Upwork, Freelancer and other sites I mentioned in my old blog. From the site's description: "Xafers.Jobs is a job service that provides xafers with pre-screened XAF jobs leads that offer real pay for real work. From web to windows to mobile, from reporting to dashboards, all of the job openings we bring you offer some form of our loved XAF framework.".
- New blog post from Joche Ojeda: Migrating XAF projects to the new version of csproj (SDK project VS2017). As you probably know, the design-time Model Editor tool supports projects with the new VS 2017 csproj format starting with v18.2. You may find this blog post helpful if you need migration instructions.
- Another blog post from Joche: Exposing your XPO ORM using GraphQL dotnet = XPO + https://graphql.org + ASP.NET Core.
- New blog post on startup performance optimization from Manuel Grundner (DevExpress MVP): How to pre cache an XAF Winforms Application. While we are at it, please do not miss the recent performance optimizations in XAF v19.1.
If you have your own blog where you share your expertise about XAF, XPO or other DevExpress products, please let us know in the comments below. If you are looking for custom XAF development or training, check out these third-party services.
Documentation updates
- We have identified the most popular class and member topics in the XAF API reference documentation based on traffic statistics. The team is now working hard to make sure that each document has a helpful code snippet. We plan to do the same for XPO API. Once we complete these initial efforts, we will select and review the next batch of popular documents. Here is the first update:ActionBase.Active, ActionBase.CustomizeControl, ActionBase.Enabled, ActionBase.ConfirmationMessage
AppearanceAttribute.Enabled, AppearanceAttribute.TargetItems, DetailView.CurrentObject
IObjectSpace.CommitChanges, IObjectSpace.CreateObject, IObjectSpace.FindObject,
IObjectSpace.GetObjects, IObjectSpace.Refresh, DetailView.ViewEditMode - New security system documents on permission calculation are available at Permissions for Associated Objects - now with schemas! Unlike simpler permissions at the object type level that you see in competitor products, the XAF security system provides more powerful permissions. They help control data access at the object type, member and object by criteria levels.
- We are working on samples that show how to use XPO with DevExpress visual controls for popular platforms such as ASP.NET Core MVC, WinForms, and WPF: https://github.com/DevExpress/XPO/tree/master/Tutorials. We have not yet provided step-by-step instructions, but you can research the source code of 10 working apps. This will also be a good start if you wish to reuse your XAF/XPO data model in non-XAF apps.
Interesting Support Center tickets
- If the ORM Data Model Designer is unavailable, make sure that you have installed Modeling SDK (or other packages like Entity Framework that rely on it) using the Visual Studio Installer (T730362).
- Due to a bug in Visual Studio versions prior to 2019, Application or Module Designers may sometimes be "lost" for the WxxApplication.xx and Module.xx files respectively. This occurs because "Subtype Designer" is added unnecessarily to xml-based files like csproj (204355).
- The parameterless IObjectSpace.CreateObjectSpace() method is hidden from Intellisense in v19.1. Use the CreateObjectSpace(Type) overload instead (BC5070).
- We performed a lot of measurements and performance enhancements for app startup and DetailView in XAF v19.1. We once again recommend that our users try Native Image Generator (NGEN) to dramatically cut loading time (T731177).
- We discussed some NGEN specificities, such as the need for administrative privileges, with other customers (T719697).
- A customer provided a sample with the XAF security system used in a non-XAF app: an OData V4 service built using ASP.NET Core (T721161).
- Several customers suggested that we change the Model.DesignedDiffs.xafml file name to better identify multiple opened tabs in Visual Studio. What is your opinion on this (T736377)?