I'm starting to design and develop a WPF application for my company and one of the first choices that I have to make is whether or not to use MVVM.
The main points to consider are:
- The application is basically a VisualStudio-like editor, where designers will create projects and will define UIs by dragging and dropping UI elements on a canvas
- I will be the only designer and developer of such application
- The project could last many months (from 4 to more than 12, depending on the features they will choose to add during the development)
- Last, but not the least, I have a very basic and "young" knowledge of the MVVM pattern and of its relative frameworks (I just developed a little test application with MVVM Light, including RelayCommands and ModelViewLocator).
What should I do? Is MVVM worth it or is it just an overkill for a solo project? Is there something newer that could be helpful also for the future (e.g. I read something about ReactiveUI, but I know nothing about how it works) or have I to continue with the good old MVC?
Thank you very much for your help!