We are about to upgrade a C# windows application (1.1) to WPF from windows controls (3.5).
The window controls (1.1 .NET) are present in a separate project within the solution together with our "entrypoint" and "process controller" for the application.
我建议从小处开始，因为学习WPF / Xaml的曲线非常陡峭，我认为一个熟练的C＃/ WinForms开发人员需要6个月的时间才能感到舒适 - 因此您的“...大型应用程序和大量业务逻辑...”可能不是一个好的开始选择。
OTOH if you re team is already upto speed with WPF, the real first step is deciding what features the users want that can be best served by the graphical niceties of WPF. If they really do want 3D spinning forms, then implement a good working prototype of that, if they want resizing documents, then do that. This is an elephant of a problem, you can only solve it a small piece at a time.
一个关键的决定是非常早期的，那就是决定是选择去用MVC还是它的各种后代。这个决定将决定你在哪里放置你的代码。由于WPF非常依赖于绑定，所以你必须知道绑定会如何、何时和在哪里发生，才能继续前进。
