Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Hosting and Servers
  4. [Partly solved ]How do I deploy/configure both an MVC solution and a separate MVC API solution to serve pages/request?

[Partly solved ]How do I deploy/configure both an MVC solution and a separate MVC API solution to serve pages/request?

Scheduled Pinned Locked Moved Hosting and Servers
questioncsharpasp-netjsonarchitecture
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    GuyThiebaut
    wrote on last edited by
    #1

    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. Update 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

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups