.net - Distributing WPF apps to a legacy user base: How seamless is it? -


I plan to develop a WPF application to be hosted by a legacy Windows app (C ++) And I'm trying to see a broad user base, I'm targeting to get a better understanding of how to do it. To know WPF target 3.5 .NET 3.5, I'm looking for some insights to see what the field looks like - already got the runtime, whether it is distributed through Windows Update, if so, (eg , An optional or necessary download, operating system etc.), even though XP pre-XP2 supports it (and how), and so on. There are thousands of users in the current version, using all types of Windows operating systems, and when I want to take advantage of WPF to breathe some life in my life experience, I want to make sure that I Not even locking it, doing so, or burdening them with a download that they may need to do manually.

I know that most of this information is already in the future, but I thought I would ask here before, because I am sure some of you probably already went under this road There are valuable experiences to share and I thank you in advance!

There are many different aspects of this question, but one important fact is that you should know that Net 3.5 SP1 supports a new technology, which enables very small and well-organized deployment based on the target that is already installed on the PC. I can tell you from the experience that without it, the deployment of WPF apps can be a nightmare and the establishment can actually do it for a very long time.

And yes, WPF requires at least XP SP2.


Comments