Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • hard to comment without seeing the code, but I think a classic razor view application would be considered a bit old fashioned today Commented Mar 7 at 10:34
  • 1
    One reason to not use WebAPI controllers in a legacy ASP.NET MVC application is that it bypasses the ActionFilters, which could include cross-cutting concerns like Auth checking, error handling, logging, etc. (So not only are you potentially throwing away some important behaviour, it's potentially also laying a "trap" for future developers to fall into too) - learn.microsoft.com/en-us/aspnet/mvc/overview/older-versions-1/… - so in general, I would stick with MVC controllers unless you have a really good reason to do otherwise. Commented Mar 7 at 13:50