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
|
If I'm not mistaken, WpfElements 6 is built only with the .Net Framework 3.5. I've used it in my Framework 4.0 application for a long time with no problem. However, a small issue recently cropped up: apparently Windows 8.1 does not ship with Framework 3.5 pre-installed, although Windows seems to detect that it is needed and offers to install it. This does make installation less convenient for our clients, and although our application is built with 4.0 we also require 3.5 (due to Mindscape). I was wondering if there are any plans to transition to 4.0 (or 4.5). I tried compiling the source code in 4.0 and immediately saw that the Microsoft DataGrid (added in 4.0) causes major naming conflicts with the Mindscape DataGrid (though it only took a few minutes to resolve these conflicts). Are there any plans regarding this? Peter |
|
|
|
|
Hello Peter We are planning to release version 7.0 of WPF Elements shortly. We will have a look at upgrading this to use .Net 4.0. I'll get back to you with how it goes. -Jason Fauchelle |
|
|
|
|
Hi Jason, I did a little further experimentation, and found that it was pretty easy to make changes to the Mindscape source code to avoid naming conflicts with the Microsoft System.Windows.Controls namespace, so that the source code can be compiled for either Framework 3.5 or 4 (and probably 4.5). I just replaced "using System.Windows.Controls;" with "using SWC=System.Windows.Controls;" in DataGrid.cs, and inserted the "SWC." where needed. I then compiled WpfElements and the Sample Explorer (samples.sln) for Framework 4 Client Profile. The Sample Explorer seemed to run fine. Would you consider making such changes to the source to enable compilation for either framework version? Peter |
|
|
|
|
Hello Peter WPF Elements 7.0 is now available. Version 7.0 is built for .Net Framework 4.0. I have done something similar to your suggestion to resolve the naming conflicts. As you are already a customer of WPF Elements, you can get version 7.0 for free from your account page. Let me know if you have any questions about it. -Jason Fauchelle |
|
|
|
