My online profile does list
NetAdvantage for Win Client 2009 Vol. 1 - WPF Source Code (Release Build Version 9.1.1006)
as the latest build.
Yet when I try to run Alex's ColumnChooser, I get the following error:
Error 1 Assembly 'MyUtilities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'Infragistics3.Wpf.DataPresenter.v9.1, Version=9.1.20091.2075, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' which has a higher version than referenced assembly 'Infragistics3.Wpf.DataPresenter.v9.1, Version=9.1.20091.1006, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' c:\temp\Infra\ColumnChooser\XamDataGrid_ColumnChooser\MyUtilities.dll XamDataGrid_ColumnChooser
Where can I find this upgrade?
We are planning on including this as a feature in 9.2 release. Forwarding to this thread: http://community.infragistics.com/forums/p/31462/172628.aspx#172628
One more question on this: In future release, are they any plan on making the column chooser dialog as a built-in functionality of Infragistics XamDataGrid?
Thanks for the quick response.
A ) Yes, we are not going to downgrade however would be upgrading and would like to know if version in the serialized string would be an issue going forward if we are to take this route. Please let me know your comments after your tests.
C) Attached (SampleLayout.txt) is what get saved when calling SaveCustomizations. If you look at it it saves the field and its datatype. Are you saying it is not being used when loading customizations or I misunderstood the usage of it?
Regarding new features in different versions, this is taken into consideration and no problem should occur with this.
A) No, it will not throw an exception if you load these settings to another version. However, there might be an issue for example from 9.1 to 8.2 as 9.1 saves filtering settings and 8.2 does not have this. I am going to test this and see if there is an issue with this.
B) To the best of my knowledge, it is not possible to exclude the version.
C) This will not matter, as the DataType is not saved, so there should be no reason for an exception here.