ASP.NET WebForms, MVC or WebAPI? [closed]

3

First of all I would like to emphasize that my knowledge in web development is very small, so my question will be focused on what to use and not how to use, since the goal is to study first and then develop.

I need to create a web application to open calls, the client should see a simple page where he will describe doubts, complaints, etc. and on that same page you can attach documents, images, etc.

This same application should contain a chat, so that customers can communicate directly with the support staff and obtain further clarification on the calls already opened.

When creating a new web project in Visual Studio 2013, I came across the templates (Web Forms, MVC and WEB API, among others). I would like to get you a guidance, like, where should I start studying to sketch an application as mentioned above.

Below are some criteria that I find important to mention for the possible decision of what to use:

  • I need to use ASP.NET, C # and Visual Studio 2013.
  • I already have a SQL Server database (currently used for the desktop application) that contains all the information that will be used.
  • In the database I already have, I already have a table with the users and passwords that they should use to log in.

Note: My intention is to know you already develop for the web, what to use and where to start, with a focus on studying to gain knowledge to start the project.

    
asked by anonymous 29.05.2017 / 14:53

1 answer

4

It's a shame to know that it's restricted to Visual Studio 2013.

WebForms is a technology considered almost legacy and weird. Some people find it easier, but have little space in the current web scenario. Do not discard it, but there are many reasons not to start something new with it, and I do not even know if there is any in your case to use it.

Since it can not use ASP.NET Core which is the most modern and it seems to me that it is important to make a complete application and not just an API, the path seems to be ASP.NET MVC.

If you need to provide an API for other programmers to communicate with your system directly without user interaction directly with your system, then you have to use ASP.NET WebAPI too (in ASP.NET Core it's one thing only).

More recently, some people are choosing to do as much as possible on the client, making Single Page Application , often with AngularJS . Then most likely only the ASP.NET WebAPI user since the MVC is used for the server to generate the pages on demand. With the use of SPA the client loads a single page and will only request data from the server.

The information to make the decision is there. Which is the most suitable for you only you can respond.

    
29.05.2017 / 15:16