XAF - Enhanced Office Module, Updated Learning Materials and More (v18.1.5)

Great news! XAF’s most recent maintenance release (v18.1.5) includes new features and updated learning materials (and of course, a few bug fixes).

New features

WinForms UI: Office Module performance enhancements

In our MainDemo app, detail forms with a RichTextPropertyEditor will now load in 0.6 sec in v18.1.5 as opposed to 2.3 sec in v18.1.4. Kudos to our WinForms team - they optimized the way in which menus are generated based on feedback they received from us.  Non-XAF forms and controls with complex menu structures will benefit as well. For the best performance, build your application assemblies under x86 and process them with NGEN as recommended in the following articles: A2670 | T1489 | WinForms Tips & Tricks - Boosting Application Performance.

As you may already know, our WinForms HTML Property Editor Module is now in maintenance mode. We recommend that you use our RichTextPropertyEditor instead of HtmlPropertyEditor for standard usage scenarios (for instance, when you wish to create email templates).


You can now embed an XAF ASP.NET WebForms app into IFRAME. This new feature will help integrate CRUD and other common XAF functionality within non-XAF Web portals. For more information, review the following support article: Q443184.

ASP.NET UI: ASPxGridLookupPropertyEditor is out of CTP

Main functions are ready and both internal and public preview tests did not reveal any show stoppers. We do not expect breaking changes either. We recommend that you use this new editor for reference properties instead of ASPxLookupPropertyEditor.

Mobile UI: Enhanced masked input

Mobile numeric, text and date editors now support formatting and thus help users avoid input errors. The familiar EditMask and DisplayFormat attributes are now used instead of the deprecated attributes with the "Mobile" suffix. You should not notice any problems, though - thanks to our IModelXmlConverter mechanism. For more information, review the following support article: T459804

Updated documentation

IObjectSpace.CreateObjectSpace(Type) is better than IObjectSpace.CreateObjectSpace() 

A best practice is to use the CreateObjectSpace(Type) method overload when your application registers multiple Object Space Providers (for instance, when it uses non-persistent objects (NonPersistentObjectSpaceProvider) and/or connects to numerous databases). This recommendation helps avoid situations wherein XPObjectSpace unexpectedly appears instead of NonPersistentObjectSpace and vice versa. 

Module Designer vs Application Designer

Settings for required modules (e.g., ReportsModuleV2.ReportDataType) are not editable in XAF's Module Designer.  The latter simply registers required module types without instantiation. To modify these settings, use the Application Designer.

New Troubleshooting Guide 

Recently, several XAFers accidentally disabled a very important Visual Studio extension (DevExpress.ExpressApp.Design.CorePackage). As a result, they lost the Model Editor's functionality - XAFML files opened as plain text. 
The new Designers Troubleshooting Guide helps isolate this and other common problems with our designers and Visual Studio itself.

The following highly rated help topics will also be of use when troubleshooting issues:

Interesting Support Center tickets

  • Three long-time customers shared their general XAF experience and XPO performance best practices (T653665);
  • One of our customers shared his custom Windows PowerShell command (cmdlet) and scripts. His cmdlet uses XAF's Object Space and facilitates long-running administrative tasks (Q476407).
  • Bing may unexpectedly translate texts with special characters, e.g. edit masks or display formats. Please be careful when you accept suggested translations in the DevExpress Localization Service (T643572).
  • We described how to calculate running totals for ListView columns using a custom criteria function and PersistentAliasAttribute (T658623);
  • We demonstrated how to customize Mobile UI appearance using custom CSS and the MobileWindowTemplate’s RegisterClientScriptXXX methods (T657883).
  • We discussed how to control the visibility of dynamically generated custom fields in Views (T654705).

Find more interesting customer questions and product enhancements for your favorite products in the DevExpress Support Center (expand the "Frameworks (XAF & XPO)" group on the right) and What's New documentation (see resolved issues). 

We need your feedback!

What do you think about these new features and the new "Interesting Support Center tickets" rubric in particular? Drop us a line below, thanks.

14 comment(s)
Yauhen Kuchynski

I often read support center to find interesting questions and advises. But sometimes don't have time or forget to do this. So of course it will be great to read such selection of the most interesting cases! Nice idea!

3 August, 2018


4 August, 2018
Dennis (DevExpress Support)

Thank you, Guys!

4 August, 2018
Norbert K.

Great features and very useful rubric!

6 August, 2018
Randy Jean

Thanks Dennis!

6 August, 2018

Dennis, do I understand correctly that an XtraRichEdit will also load faster in WinForms in 18.1.5?

6 August, 2018
Dennis (DevExpress Support)

@Jean-Francois Cosse: Yes. Non-XAF forms and controls with complex menu structures will benefit as well.

6 August, 2018
Brad Baker - MMC

Are there plans/new framework that will move XAF out of this legacy code base?  This is just something that no one in their right mind would use today if starting a new project.  There is no way for me to justify using winforms/and webforms in todays environment.  Wouldnt some kind of web based electron version be a viable option?

6 August, 2018
Sigurd Decroos _

^ What Brad said!

10 August, 2018
Andy Yin (BOI)

Very Good!

20 August, 2018
Dennis (DevExpress Support)

@Brad Baker - MMC, Sigurd Decroos:

I wanted to share our updated vision for XAF Web & Mobile development – one that’s based on an entirely new SPA driven UI. When this ASP.NET Core and React-based solution matures, it will supersede/replace existing WebForms and Mobile user interfaces.

Right away, existing XAF Mobile UI users are welcome to migrate to our newest server features: How to connect an existing XAF Mobile application to the new ASP.NET Core Data Service (CTP). The new SPA UI will use this server and you can help us release this portion faster by providing feedback.

We hope to publish new SPA UI demos online after our v18.2 release. In the meantime, anyone is welcome to check screenshots of our prototypes and discuss their specs in our forum with peers. No promises at this stage, but our hope is to offer this SPA UI for production use around the v19.1 timeframe (at least for simple scenarios).

20 September, 2018
David Shannon

I'm doing some testing with the RichTextPropertyEditor and have questions about Styles:

(1) Are the styles stored in each individual document (using DOCX format)?

(2) If so, will it ever be possible to have a global format (like the normal template in Word) so that styles can be made standard over multiple documents -- preferably the entire database?

(3) Can the list of styles be extended through the UI?


8 October, 2018
Dennis (DevExpress Support)

@David Shannon: We'll answer you in the Support Center ticket, if you do not mind: www.devexpress.com/.../office-winforms-richtextpropertyeditor-styles.

8 October, 2018

There is a problem with replacing Html Editor with Rtf Editor . In example RTF Editor is not compatible in 100% with HTML - i.e. there is limit for number of div tags (T677781).

12 October, 2018

Please login or register to post comments.