Should I choose ASP.NET MVC or SharePoint for Enterprise?

Question

SharePoint

Good evening everyone. I will have to start developing the system. Give them time to decide what to use. But experience is only in ASP.NET MVC. After reading some articles, I began to doubt my initial choice of MVC. SharePoint also seemed attractive with its pluses. The system that is on ASP.NET MVC, that on SharePoint will have to be implemented from scratch. The choice of technology for system development is to be made from the Microsoft stack. It is very important to hear the opinion of more experienced and authoritative people on the account. If possible, please tell me from your experience or knowledge how ASP.NET MVC and SharePoint fit these criteria:
At work, it will be necessary to implement a system of analytical reporting. Containing various reports with a lot of data, column fields and filters, detailed reports, etc. Now it is implemented in its own reporting system, but leaders want to see a more modern design and support in browsers. Also, at the moment the system works in the local network of the organization, but it will be necessary to provide access to reports via the Internet.
Initially, the plans were to implement the system on ASP.NET MVC 5. But the management remembered that SharePoint was purchased in the enterprise (2010 or 2013). It is integrated with Lync and Outlook, which is handy. The question is what to use.

1. Creation of a convenient user interface (rather ease of creation, because Bootstrap will most likely be used;
   
2. Simplicity and speed of development (given that the development will be from scratch and my knowledge is limited to ASP.NET MVC);
   
3. Ability to easily deploy and configure the server for access from the Internet;
   
4. Security settings: authorizations, roles, encryption, etc.;
   
5. What else do you need to pay attention to?
   

Answer 1

SharePoint makes it easy and fast to implement many things. But it's worth considering:
1. SharePoint is a bigger and scarier ASP.NET WebForms application. No matter what anyone says, ASP.NET WebForms will gradually die off. Do you want to study this dinosaur?
2. Very scary HTML, which will be quite problematic to modify. For example, you will need to make a version for mobile devices.
3. Very little good documentation. Often you will find WRONG answers to your questions.
4. The list system will blow your mind. A bunch of unnecessary fields. A bunch of names for one field (StaticName, InternalName) and different functions use different names.
5. Non-obvious behavior of some things. Tell for a long time. Just take my word for it.
6. Closeness. If you suddenly need to fix something... then you can't.
My advice: if the functionality of SharePoint 100% covers the requirements of your organization (exactly 100%, not 99.9% even), then you can try. Otherwise, it's better to write from scratch. Because sometimes even small changes require a huge amount of code.

Answer 2

SharePoint development is fucking hell.
I myself do not come across very often, but all my colleagues are developed spit, and they have been doing this for a long time and being a pro in it. If you are not a developer, then you should not contact him. Absolutely not worth it.

Answer 3

asp.net mvc is enough. Sharapoint can come in handy if you want more direct access to the domain, accounts, AD, and more. You can try to combine business with pleasure - create a Sharepoint application, and inside it MVC as a component. I worked at a later stage with such an application, but I do not remember how it was implemented.

Answer 4

By and large, according to my great and thorny experience in developing SharePoint, and I can say about it since the 2003 version, what is now in the 2013 version is a flying tank that has a lot and it may simply not reach the development of custom solutions. It is quite rich in functionality, if you understand it, and out-the-box has a lot of corporate goodies. But there is a big BUT, in Russia the management and top management of companies really like to redo everything or file it with a design, etc., that's when HELL begins with a capital letter. increasing functionality (even custom ones) within the default UI is easier and cheaper.
As for MVC, you will have to assemble this flying tank yourself like DYI =) And with SP you already have it, you just need to read the instructions for use and examples of adapting this or that feature and there further according to the situation.

Answer 5

The ball has its own ideology, which will have to be taken into account in development. As Viktor Buzin has already said , a ball is a tank and it has a lot, although not all, of useful things.
If you take a ball, then keep in mind - this is not a database. You can't do complex data queries (with a bunch of relationships). For analytics, it is better to use another tool.