|I have a .NET MVC website live which also served as a test API - the solution both served standard web pages as well as API calls.
I decided that I wanted to separate the website and API so I now have two solutions.
I have amended the RouteConfig.cs for the website so that it no longer serves API routes.
How do I go about configuring things so that both the MVC website dll and the MVC API dll are accessible?
I uploaded the API dll and using postman I could see that the API service was not responding to the requests I sent.
I am guessing there is something I need to do with the web.congig or global.asax files that's as far as I have got so far(guessing... and some googling of course...).
Thank you for any help or direction in where to look for information - I don't think I have been asking the right question for Google searches so far.
I have now partly solved this by creating two projects within one solution and referencing the API dll from the main application, including a route mapping for the API within the non API project.
It's a bit messy but will do for the moment.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 24-Mar-18 5:58am.