Hi,
We've been using the Telerik WPF and Telerik Reporting .Net 4.0 codeset to write our desktop application code. However, we're having a lot of clickonce installer issues related to end-users not having .Net 4.0 installed on their machine. Bundling .Net 4.0 with our installer creates an undesirable user experience in several ways. We're considering reverting our entire codeset back to Telerik WPF 3.5 as a last resort if we can't fix our installer issues.
Alternatively, is it possible to keep our code with Telerik WPF/Reporting .Net 4.0, yet make the application backwards compatible with machines that have only .Net 3.5 installed, so the user doesn't need to install .Net 4.0?
Thank you, TJ
We've been using the Telerik WPF and Telerik Reporting .Net 4.0 codeset to write our desktop application code. However, we're having a lot of clickonce installer issues related to end-users not having .Net 4.0 installed on their machine. Bundling .Net 4.0 with our installer creates an undesirable user experience in several ways. We're considering reverting our entire codeset back to Telerik WPF 3.5 as a last resort if we can't fix our installer issues.
Alternatively, is it possible to keep our code with Telerik WPF/Reporting .Net 4.0, yet make the application backwards compatible with machines that have only .Net 3.5 installed, so the user doesn't need to install .Net 4.0?
Thank you, TJ
1 Answer, 1 is accepted
0
Chris Gillies
Top achievements
Rank 1
Rank 1
answered on 11 Feb 2012, 01:33 PM
The logic is backwards, you build applications with the lowest version possible, that guarantees that they would work on the latest version, the same logic is used in bindingRedirects - you can redirect only to newer versions. Don't see how you can do the opposite.
Cheers!
Cheers!