Asp.Net Razor with Json

Question

I have a question and I have researched several sites but I did not get the answer. I develop systems in .Net with C# in MVC standard and use the on-screen presentation in the traditional View with Razor.

It happens that I have noticed that several web systems made available lately have presented more and more a user experience like a Desktop application, that is, with almost no Reloads per request and a greater interactivity with the events of the fields.

Many of these systems use Knockout, Vue, Aurelia and mainly Angularx in their Views, or better, use only the MC and the V is on account of other technology.

Now comes my question, how do I not master any of these technologies (yet), with your experience, what would be the best way to work with Views in such a way that I could create the systems with a user experience closer to those provided by the technologies mentioned above maintaining the MVC development standard with Razor? By the power that Views generated with Razor offers, a lot probably I shouldn’t be using some resource that this tool can provide?! - So I could observe one of the things that "must" work to arrive at the expected result is to work with Json (so far so good) as if my application were a Web API - I’m sure?

I hope I was clear in presenting my doubt.

Thanks in advance for the strength!

Answer 1

From what I could observe one of the things that "must" work to get the expected result is to work with Json (so far so good) as if my application was a Web API - I’m sure?

Even better: working with the Web API itself. The Web API emerged precisely in its finding: how to make the MVC system work without relying on the presentation layer?

what would be the best way to work with Views in such a way that I could create the systems with a user experience closer to those provided by the previously mentioned technologies while maintaining the MVC development standard with Razor?

First, developing methods that respond to the new presentation layer within the MVC system itself. Then migrating this structure to a purely web API system. I have a course that explains how to do this, if interested (the menu is the same).

That is, given a method that normally returns a View:

public ActionResult DevolveView()
{
    ...
    return View(objetos);
}

You make a copy of this method in order to return a structured JSON:

public JsonResult DevolveView()
{
    ...
    return Json(objetos, JsonRequestBehavior.AllowGet);
}

And then create a Controller separately for these new methods using JSON:

public MeuControllerApi : ApiController
{
    public IHttpActionResult DevolveView()
    {
        ...
        return Ok(objetos);
    }
}

This is just a suggestion. The ideal is to make a denser tutorial to understand how this migration works.