Popularity of MVP for SharePoint WebParts

Question

Is a popular technician using the View Viewer (MVP) design pattern when creating web parts for SharePoint? It seems (to me) that this template is used more often in the user space of the application. So, if you have any thoughts on this, please share ...

[Change]
Perhaps a more important question: if MVP is less popular in a SharePoint web environment than in a user application, why do you think this is (what factors contribute to this observation)?

Answer 1

This is probably not very popular, but it is also probably good design practice.

Perhaps the more important question is if MVP is less popular in SharePoint WebPart than in a custom application, why do you think this is (what factors contribute to this observation)?

This is a "new" approach in the SharePoint world. Everyone is used to doing this in the old way of SharePoint. This also applies to ASP.NET and ASP.NET MVC.

MVC and MVP patterns are becoming more and more popular because they allow you to “separate” the presentation layer from the underlying logic, essentially “compromising” the user interface.

Personally, I think that everything that makes SharePoint a simpler programming platform is a pleasant relief.

Answer 2

Since SharePoint is not compatible with ASP.NET MVC? It was planned somewhere on the line. you do a lot of plumbing before you can get any functionality, and I suppose that of all the web parts created for SharePoint, most of them will not be very complex, because they are likely to be only a small part of the complete -SharePoint solution.

Here is someone who built something like this, like: ARF

Answer 3

I have developed several web pages for SharePoint using the MVP template, and I find this pretty good in terms of validation. However, I found the following problem: If you have a website with a custom EditorPart panel (a panel with custom properties), then decoupling via MVP is not easily achievable, since the data from Toolpart is stored back to WebPart.

Second: I do not think that the MVC template will be available soon in SharePoint (my opponent, I am not an insider), the impact will be too big. However, there is SharePointMVC

Framework This has a pretty big drawback: you need to create a separate WebApplication for it.