New version of the DXCore XPO plugin - help me test!

XPO Team Blog
09 March 2007

I've prepared a new version of the XPO plugin for DXCore. For those of you who haven’t used that plugin before – here’s the introduction of the “Simplified Criteria Syntax” feature. Once the new plugin version has been tested, I’ll have to make some changes to that page…

Here’s the download of the new plugin version: (18330 bytes)

Note: please make sure that this is the only version of the plugin you are using! I’ve seen a case in the past where there was more than one version of the plugin installed (several copies of the assembly in the plugin folder, with different names), and of course this results in some weird problems…


So what’s new in the new version? A whole bunch of things. See here, and read carefully:

It is compiled for .NET 2. It will not run with .NET 1.x.
Of course this means it can only be used in Visual Studio 2005.

It creates code that is only compatible with XPO version 7.1 and later.
The 7.1 RC that is currently available can be used with this plugin version, but no version earlier than that. My plan is to “backport” some of the bug fixes to a version of the plugin that will be the final version made available for .NET 1.1 compatibility (XPO 6.3 and older).

It is compiled for DXCore 2.1.3.
In my experience, compatibility with newer DXCore versions should be very good (although we’ve seen breaking changes in the past, if rarely), older versions will not work.

There’s rudimentary logging support
The plugin can log some information to the CodeRush Messages window. This can be helpful to track down bugs. The Messages window can be accessed from Visual Studio via the menu – DevExpress | Tool Windows | Diagnostics | Messages.
The plugin has a new option “Logging active” that enables logging, it’s disabled by default.

The structure of generated code has changed
I have changed the structure of the code that the plugin generates. The reason for this is a suggestion submitted by a customer (thanks!), and the new structure allows using “long”, i.e. concatenated property names in queries (OrderLine.Fields.Order.Customer.CompanyName == “Developer Express”).
The plugin has been changed to remove any old-format Fields class automatically and create the new structure instead.

“new” and “Shadows” are now applied correctly (AB7485)

“Persistent”, “NonPersistent” and “PersistentAlias” are interpreted correctly (CB18441)

Outstanding issues

Apart from ideas I have – of which there are quite a few –, there are also issues that are currently active in our support center, but haven’t been addressed in this release. I want to mention two such issues here:

CS30989 – this is about the complex situation where classes in a hierarchy are partly persistent, partly non-persistent. It will require some thought to come up with a good implementation of this.

CB8627 – this bug is about the problem of incomplete structures. As I have previously reported in the issue comments, this is a problem without an easy solution at the current time, as the DXCore parser isn’t able to deliver the information I need. I have some ideas for workarounds in this area and I’ll try to implement them – a complete solution of the issue may only come along with the introduction of a new parser in DXCore.


I have done a lot of tests on this version, both in C# and VB.NET, but I’m absolutely sure there are more bugs in there that can be found. I’m planning to quickly fix any problems that are reported in the near future, and release another updated version soon. Of course this will work only if at least some of you download the current version and test it :-) I’d appreciate it if you did that and helped me with your bug reports – preferably please enter them in Support Center, so I can easily track them.

Free DevExpress Products - Get Your Copy Today

The following free DevExpress product offers remain available. Should you have any questions about the free offers below, please submit a ticket via the DevExpress Support Center at your convenience. We'll be happy to follow-up.
No Comments

Please login or register to post comments.