<p>How stable is WPF not in terms of stability of a WPF program, but in terms of the 'stability' of the API itself.  </p>

<p>Let me explain:  </p>

<p>Microsoft is notorious for changing its whole methodology around with new technology. Like with the move from silverlight 1 to silverlight 2. With WPF, I know that MS changed a bunch of stuff with the release of the .NET service pack. I don't know how much they changed things around. So the bottom line is, in your opinion are they going to revamp the system again with the next release or do you think that it is stable enough now that they won't change the bulk of the system. I hate to have to unlearn stuff with every release.  </p>

<p>I hope that the question wasn't too long winded.</p>

[{'answer_id': 31485, 'author': 'Matt Hamilton', 'author_id': 615, 'author_profile': 'https://Stackoverflow.com/users/615', 'pm_score': 5, 'selected': True, 'text': '<p>MS do have a history of "fire and movement" with regards to introducing new technology into their development stack, but they also have a strong history of maintaining support for the older stuff, and backwards-compatibility. WPF seems to be getting stuff added to it with each new release of the framework but the things you learn aren\'t being superceded or invalidated.</p>\n\n<p>The only breaking change I\'ve seen in my own WPF applications with a new release of the framework was one recently in 3.5 SP1, and that was because we were unknowingly relying on a bug to get a certain behaviour from our code. We adjusted the XAML to be more correct and it started working fine.</p>\n\n<p>So yeah, I think WPF is pretty "stable" as a client-side development technology.</p>\n'}, {'answer_id': 31491, 'author': 'Dale Ragan', 'author_id': 1117, 'author_profile': 'https://Stackoverflow.com/users/1117', 'pm_score': 2, 'selected': False, 'text': "<p>We've been using WPF since it was first released and yes it had it's problems at the beginning that caused us headaches and had us scratching our heads to find a work around, but each new update the stack has actually become pretty stable.</p>\n\n<p>It definitely became easier and easier to develop with it with the addition of Expression Blend.  Creating the XAML in VS 2005 was not fun.  The templating engine alone is enough to switch from WinForms, let alone the animation support.</p>\n\n<p>Either way, I agree with Matt that it is pretty stable as a framework for developing client applications.</p>\n"}, {'answer_id': 31527, 'author': 'Brian Leahy', 'author_id': 580, 'author_profile': 'https://Stackoverflow.com/users/580', 'pm_score': 0, 'selected': False, 'text': '<p>WPF is pretty stable as far as changes go.  Silverlight is still in flux.  Though you may watch out since silverlight brought the concept of the state manager(instead of implementing triggers) which may get adopted in wpf... </p>\n\n<p>If that happens there will be multiple ways to defining control templates and behavior...</p>\n\n<p>and that will be a headache.</p>\n'}]
['https://Stackoverflow.com/questions/31480', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/2976/']