Is it too late to implement an architectural pattern like MVC or MVVM?
I was released to version 2 of an application that my company is working on. This was our first foray into WPF and of course there were many tutorials. The product took a year to develop, so it is not a small application by any means. Everyone recently came on board with MVVM.
Now that we have a large codebase with a lot of x: Name and a lot of logic in our code support files, is it too late to switch to something like MVVM moving forward? Keep in mind that it is probably not in the budget to go back and modify existing windows to accept this pattern, so there will always be a mixture of both should you adopt MVVM in the future.
Evaluate opinions on this issue.
a source to share
I was in a similar situation. We started our WPF application while WPF was still in beta, and of course we made a lot of mistakes in the early days. When we learned about MVVM, it became clear that it was much better than our "MV" approach.
We already have a fairly large existing code base and it was unrealistic to stop what we were doing and convert to MVVM. We have decided that all future developments will use the MVVM pattern and we will gradually move the existing code base. Basically, whenever we needed to change an existing screen, we used this opportunity to refactor and convert to MVVM.
This approach worked well and today the entire project is using MVVM.
a source to share