Run a web app from another web app in visual studio

Question

0.00/5 (No votes)

See more:

I have a asp.net solution that contains several web apps. When deployed, the main app can run the other apps (via a url of course). Is is possible to run them locally on localhost?

What I have tried:

Nothing but copious googling and hoping for the best. Maybe my google foo is not effective today.

Posted 28-Jan-19 0:57am

#realJSOP

Updated 28-Jan-19 4:30am

Add a Solution

Comments

Richard Deeming 28-Jan-19 7:33am

Are you looking for multiple startup projects[^]?

#realJSOP 28-Jan-19 7:43am

No. I want to be able to click a link in one web app that runs another web app in the solution.

ZurdoDev 28-Jan-19 8:06am

I don't quite follow. "Run" a web app really just means go to a url. So, yes, certainly you can go to any url.

#realJSOP 28-Jan-19 8:26am

By "run an app", I mean click a link and have it start. When you run a web app in VS, the url is localhost:nnnnn. To my knowledge, you can't set a url (in a link) to "localhost:nnnnn" and have IIS express understand what you mean ("run this app over here").

ZurdoDev 28-Jan-19 8:28am

No, you would go into VS and right-click your project, properties, click the Web tab and then put in a specific Start URL with a port. Then go into IIS and configure the site on that port. In other words, set it up in IIS so that it is always the same port instead of letting VS control it and getting different ports numbers.

Richard Deeming 28-Jan-19 8:09am

I haven't seen any way to do that other than multiple startup projects, or manually starting the other application from within Visual Studio before you click on the link.

#realJSOP 28-Jan-19 7:52am

I want to redsign the app to use MVC Razor Pages, and move all of the apps into a single app. I'm going to have to do this on my own time because we don't have "time or people" to do it at work. Unfortunately, on a team of eight developers, I'm the only one willing to put in the time. :(

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2019-01-28T04:31:00

A website needs to be hosted in a unique host\port configuration so "localhost" is really "localhost:80" as it defaults to 80. If you want to run multiple sites on the same server you need to either give them unique ports or unique hosts (or both). So you have to give each site a fixed port and always use that port and any links to that site would be in the format

localhost:xyz/somepage

In IIS you'd then create a website for each one and bind it to the relevant port. The alternative is to give each its own host, so you would have

sitea/somepage

and so on, and again in IIS create each site and bind it to your given host. Your problem then is making that host resolve to the target machine. If this is localhost for testing then you can amend your hosts file to configure each host to resolve to 127.0.0.1