Is rewriting a product in WPF a good idea if your customer base still uses XP?

On this site alone there are numerous examples of problems with WPF associated with XP. Eg:

• Font problem in windows xp
• some troubles with WPF and Windows XP
• WPF Combobox rendering on XP
• WPF Child Windows problem in Windows XP
• WPF video tearing on Windows XP
• MenuItem blue on hover in xp, fine in windows 7
• Why does my WPF application quit unexpectedly on Windows XP SP2?
• XamlParseException on Windows XP
• XamlParseException in WPF application - but only on when installed on XP
• WPF render glitches on WIN XP
• Running a WPF application on Windows XP

If my client base still uses XP, is rewriting my VB6 product in WPF a good idea at this stage or should I just go for Winforms for now and leave WPF until the clients have upgraded from XP?

I have worked on a very large, complex application in WPF which would run on XP perfectly. Yes there are probably a few issues which MAY arrise but this does not mean that you should avoid WPF entirely.

If you are going to rewrite your application WPF would be a great way to go, you can do a lot more with the UI and although there is a learning curve it is not too steep and the benefits outweigh the drawbacks.

I would say migrate the product into WPF, keep the old one around for legacy purposes if users dont want to upgrade, you can probably reuse some of the code from your existing application anyway in the WPF one so maintaining both may not be as bad as you think.