Vulnerability in EPiServer.Forms
Hi allwe have a solution that we would like to upgrade to MVC instead of Web Forms and we are well aware of all the technical advantages we will get but that does not act as a argument fully for the customer.
Do you have any "feature based" reason what we can use when talking to our customer why they should upgrade? One example is Episerver forms, it runs only on MVC and that is a good one, but do we have any more similar reasons we can could use :)? Just give us all reasons you can think of :D!
And as i said, we know about all the other good reason why choosing mvc :=) Thanks for all the input.
One of the reasons is that Commerce after 12.0 will not be tested with Web Forms. Well - you might not be using Commerce in this project, but it's good to know, I suppose. By "not tested", I mean that i might still work, but we no longer guarantee that, and won't fix any Web Forms-specific bugs.
MVC is the way forward so I don't see any reason why not to :)
ok, is similar planned also for the CMS?Because that would be a very good reason. Also im not looking for reason to stay on web forms :), we really want to move the platform to MVC but we need more arguments in form of "we will be able to do this cooll stuff if be upgrade" just give the cusotmer all the reason we see is not enought. They want more, for example what new feature would they be able to implement that are not possible with web froms.
Episerver Forms is one of them but we need more :)
Moving to MVC would make a transition to .NET Core possible when Epi supports it fully.
Then again the argument could be to not port Web Forms sites to MVC until then
Mvc has slightly smaller code footprint (less symbols) - makes readability better.
Other good reason generally of web forms and MVC:
As Quan said earlier right now Commerce will not test their solution on webforms and I will think that this could also happen to CMS part.So, see it as future-proofing the solution
thank you for all the answers :)!