This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, I've attached a very simple sample application which doesn't work in Vista without SP1 but it does in Vista SP1 with .NET Framework 3.5 SP1. In Vista .NET Compact 3.0 makes application crash. Is mandatory for me that it must works in Vista without SP1 and .NET Framework 3.0 without SP1. What can I do? Or am I using something wrong?
Thanks. PD: I am using Mindscape.WpfPropertyGrid.dll version 1.0.0.0 from 29/01/2008. |
|
|
|
|
Hello Josep, The WPF Property Grid requires .NET Framework 3.0 SP1 or above. Sorry! |
|
|
|
|
Oh my God! Very bad news! For me is very important to know exactly WHY don't work with 3.0 without SP1. Which is the feature you use in 3.0SP1 that cannot be used in 3.0? Maybe you should make clearer this point before buying it because there are a lot of developers ( like me ) that we must ensure compatibility from 3.0 to 3.0 SP1. Who knows If I had know it before ...
Thanks |
|
|
|
|
Hello Josep, The standard editors use the ValidatesOnExceptions and ValidatesOnDataErrors properties of the Binding class. These were only added in 3.0 SP1. You may be able to get around this by replacing the standard editors with lookalikes that don't perform this validation (or perform it in a 3.0-compatible way). I will look into this urgently and let you know. |
|
|
|
|
Hello Josep, Well, I have some good news and some bad news. The good news is that if you replace the standard editors with lookalikes that do not use the SP1 Binding properties, then it appears you can run the grid on .NET 3.0 RTM. I understand that you have the Enterprise Edition of the grid, so you can essentially copy the templates out of the source code in Editors.Generic.xaml (and their dependencies in Common.Generic.xaml), remove the offending properties and paste the updated templates into your Window.Resources section. We would be happy to provide assistance or samples (by email) if required. Please note we have not performed extensive testing of this approach so you may still run into some issues that we have not proved. The bad news is that recent nightlies have another dependency on SP1, namely the INotifyPropertyChanging interface. I believe you are using the RTM version of the property grid, so this will not affect you directly, but it does cut you off from our delivery mechanism for bug fixes and feature requests. Fortunately, there does seem to be a way to break this dependency, but it does require changes to the property grid code. These changes are very messy, so I will not be applying them unless we need to make a fix for you (and I will be planning to roll them back in 2.0), but it does mean you will not be completely cut off if you hit a real showstopper problem with the RTM version. Again, to reiterate, this additional dependency does NOT exist in RTM, so as long as you are using that version (or nightlies prior to July 2008), you should be able to run on 3.0 without SP1 once you override the editors as described. Hope this helps, and please don't hesitate to contact us if you need help or guidance getting this working. |
|
|
|
|
Hi, I've implemented changes in Editors.Generic.xaml and all works perfectly! It's a pitty I cannot use nightly builds but, at the moment, I can go on.Thank you very much. |
|
|
|
