CODEWITHSUNDEEP
asp.netangularjsiisasp.net-web-api
Valerio
Valerio

Reputation: 3615

How to deploy a single solution with multiple projects?

I have developed a well-decoupled website using WebAPI and AngularJS as follows:

SOLUTION
  |—— WEB.API Project  
  |—— Website pages Project
  '—— Other projects related to functionalities

This setup is on my own computer.

Now I'm here wanting to deploy to my web server (iis 7.5, privately owned, WebDeploy installed). It is possible to deploy both projects on a single web site? (other projects are class libraries, so no hassle)

For what I know, I have to deploy the WebAPI part to a website, and the UI part to another website. May I put them on a single website?

Upvotes: 6

Views: 5007

Answers (4)

Christian Phillips
Christian Phillips

Reputation: 18769

You could also self-host the Web API using OWIN, so you wouldn't then need to set up a project in IIS etc and you could then have multiple clients talking to the same API.

There's a tutorial here which is more advanced.

Upvotes: 1

BMac
BMac

Reputation: 2230

I have a near identical project setup. Personally I picked 2 separate apps, I have a multi server setup with load balancers - the choice may have been different if I had a single server or low amount of expected traffic.

This gives the advantage: I expected my WebAPI to have a larger amount of traffic than the web pages, due to mobile clients also consuming the WebAPI as well as the front end webpages. Because the API is in its own website, it has its own app pool - this means that each application has its own resource pool (app can grow to use more memory and CPU better), not shared like they would be on a virtual directory.

Disadvantages: Because there is two separate app pools, I have one bound to port 80 and the other to port 8080. As I had a large server farm to roll this out on, I already had a load balancer in front of the webservers - hence to make the URL pretty (i.e. drop the port 8080 from the URL) i added a load balancer config to allow traffic to come in on a given url on port 80 and be redirected to port 8080 on the internal webservers. This isn't really a issue if you don't mind ports in your URL's.

Upvotes: 1

Patrick Hofman
Patrick Hofman

Reputation: 157058

You can, but you should be worried when files conflict. If both projects have a web.config for example, this could break either of them.

If not, it should be possible, but I wouldn't immediately recommend it. I would split them off in separate virtual directories so you can maintain the two separate projects easily.

Upvotes: 2

Paolo Costa
Paolo Costa

Reputation: 1989

You can put the Web API project in a virtual directory under the main web site. That's what we are actually doing in our current project.

Upvotes: 2

Related Questions