Nightly news, 12 November 2010

Big news this week has of course been the release of our Silverlight Elements 2.0 control suite — and don’t miss the free book offer for all customers. Of course, we’ve also been busy keeping up with fixes and enhancements on our other products as well. Here’s what’s new in this week’s nightly builds.


  • We’ve made the “can’t synchronise external class references” designer warning a bit more restrained if you have a lot of classes derived from an external base.
  • Fix for a designer bug where if you selected an entity in the tree view, then hit Del in the filter box, it deleted the entity
  • Fix for an issue with soft delete and joins
  • Fix for an issue with discriminated inheritance and joins

WPF Elements

  • Added support for custom object creation in the property grid “new collection item” button
  • Added work hours customisation to the Scheduler control

These are all available now and you can get them from the usual places.

Nightly news, 15 October 2010

So, did we manage to ship any fixes or enhancements while engaging in our week-long bloggy beardgasm? You bet we did! Here’s what’s new in the latest nightly builds.

Silverlight Elements

  • Added a DataLabel property for all data series (except BubbleSeries — get a real chart, bubble fans!)
  • We’ve changed DataSeries to use a consistent SeriesBrush property, replacing the old BarBrush, BubbleBrush and BogBrush properties


  • Fixed an error in the LINQ provider if a query traversed a one-to-one association from the end without the foreign key
  • Fixed an aliasing error with value objects in a derived table
  • Fixed an aliasing error in Exists queries with certain database providers
  • Migrations extensibility for full ninja support — we’ll write about this when we’ve had a bit more feedback from users

NHibernate Designer

  • Fixed an issue if a property coincided with the discriminator

WPF Elements

  • Fixed an error in the property grid if the selected object raised PropertyChanged with a null or empty property name
  • Some updates to the MultiCalendar generic style

Where can you get them? From the usual places. When can you get them? Right now!

Nightly news, 17 September 2010

Another week draws to an end and we have a bumper crop of features and fixes in the latest nightly builds. Get ’em while they’re hot!


  • Added support for using the “is” operator on associated entities in LINQ queries
  • Added support for using non-database-backed properties in LINQ expressions
  • Added support for string concatenation in LINQ expressions on non-SQL Server databases
  • Added wildcard column exclusion to lsgen command-line tool
  • Provided a more meaningful error if the LockVersion field was declared incorrectly
  • Added an option to have sequence allocation run up to the returned sequence value instead of behind it
  • Fixed a bug with function arguments which themselves had functions applied to them
  • Fix for nested Any calls in a Where clause where the nested Any doesn’t have a predicate
  • Fixes for designer NoReverseAssociationAttribute support
  • Added fixes for hyphenated domain names in SimpleDB
  • Provided a workaround for Visual Studio 2010 Server Explorer not allowing connections to SQL Server 2000 except through OLE DB

WPF Elements

  • Fix for drop-down not appearing for enum values in the property grid when displaying a weak-typed ObservableDictionary
  • Added RichTextBox support to the PromptDecorator

WPF Diagramming

  • Tweak to make it easier for applications to detect when diagram elements have moved

Free editions from the downloads page, retail editions from the store.

Changes to the WPF Property Grid in WPF Elements 3.0

As we’ve previously mentioned, as of WPF Elements 3.0, the WPF Property Grid is now part of the Elements suite and is no longer available separately. If you’re a WPF Property Grid customer, this means there’s good news and bad news.

The bad news is that we’ve made some minor changes as part of the move, which may require some updates to your code. These changes are as follows:

  • The PropertyGrid control is now part of the Mindscape.WpfElements namespace. If you have code-behind which refers to the PropertyGrid type, you’ll need to update your using/Imports statements. Also, if you’ve used a clr-namespace XAML namespace instead of the http namespace, you’ll need to update your XAML.
  • PropertyGrid support classes such as Node and Editor are now part of the Mindscape.WpfElements.WpfPropertyGrid namespace. Again, if you’ve got code which refers to these types, you’ll need to update your using/Imports statements.
  • The implementation of the NumericUpDown and Date editors has changed to use the WPF Elements numeric and date controls. If you’ve custom styled these editor, you’ll need to update your style. See the example styles included with WPF Elements for examples.
  • There’s no longer a built-in masked text editor. You can however create your own using the WPF Elements MaskedTextBox control.

If you don’t want to make these changes, of course you can carry on using the Property Grid 2.x DLL — just save it and your licence file to a private project location (such as an Assemblies or ThirdParty directory) and reference it at that location. Or if you need help making the changes, jump in on the forum and let us know what the problem is.

What about the good news? Well, the good news is that all current WPF Property Grid customers receive a free upgrade to WPF Elements 3.0, which means you now get a whole truckload of cool controls thrown in alongside the grid, from basic business controls like the CurrencyTextBox to advanced business controls like the Scheduler and controls like CoverFlow that just add a touch of glamour to your user interface! Get the full details here and download your copy from the store!

Nightly news, 30 July 2010

We’ve been busy this week nailing down the hatches on WPF Elements 3.0, but we’ve also got a bunch of stuff into the latest nightly builds. Here’s what’s new.


  • Now you don’t even need to leave the designer to get your database created. If the designer can’t find the database when you try to do an Update Database, it will now offer to create it for you — if you’re on SQL Server, MySQL or PostgreSQL, anyway. Let us know if you want this feature for other databases too. (Except Oracle. If you want it for Oracle… please don’t let us know.) Rumours that the next version of the designer will download and install the database software for you are greatly exaggerated.
  • Fixed an error with client-side boolean literals.
  • Fix for an error when projecting a property declared in a derived class when using class table inheritance.
  • Fixed an issue where discriminators were not respected when joining to a derived class.
  • Beta support for the SQL Server Compact 4 CTP. This requires an additional assembly reference: see here for instructions. At the moment, this is only runtime support: there’s no designer integration. Of course you can still use designer-built models with the LightSpeed runtime, you just won’t be able to do database sync or migrations.
  • Ninja association support, or ‘cross-cutting composite keys’ as they are more prosaically known. We’ll post more about this later, but if you can’t wait, see here for the details.

WPF Property Grid

  • Fix for an exception when editing a subnode in a collection when the collection contains expandable structs.

Don’t forget the WPF Elements 3.0 beta is now available to existing property grid customers. This contains some changes to the property grid so check it out sooner rather than later!

WPF Flow Diagrams

  • We’ve added some hooks to make it easier to serialise custom connections. Here’s a sample.

All these features and fixes are available in current nightly builds — get free and trial editions from the downloads page, or retail versions from the store.


Join our mailer

You should join our newsletter! Sent monthly:

Back to Top