Deploying a .NET MVC web application to a subdirectory in IIS

Question

I'd like to create a web application in IIS containing a site and then have a subdirectory, either a virtual directory or another web application, containing a .NET MVC application and configure the routing as appropriate.

As my MVC application is fairly straightforward, I only need one controller so I'm hoping that URLS such as:

http://mysite.com/mvcapp/

will map to the Home controller of my application. This seems as though it should be simple enough to implement however actually setting this up seems to result in errors such as:

HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.

If anyone has any experience in these sort of issues, your guidance would be much appreciated!

Erik Funkenbusch · Accepted Answer · 2012-05-29 14:55:20Z

1

It sounds like you did not set the folder to ba an application running the correct version of asp.net. How you would do that, depends on the version of IIS, whether you have access to IIS Manager, etc...

answered May 29, 2012 at 14:55

Erik Funkenbusch

93.6k29 gold badges201 silver badges292 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

rwbutler Over a year ago

Thanks for the suggestion. I have full access to the server. The issue is really a routing one. The application pool is running the correct version of .NET.

Erik Funkenbusch Over a year ago

@rwbutler - it's unlikely to be a routing problem. The fact you get a "unable to list contents of directory" means that .NET isn't even being executed.

Zach dev · Accepted Answer · 2012-05-29 15:03:37Z

0

check some details

is running the site with the correct app pool configure to the target framework? (v4.0 guess so)

check out the registration of framework on iis, sometimes the registration is needed (again)

Type cd C:\Windows\Microsoft.NET\Framework\v4.0.30319\ Type
aspnet_regiis.exe -ir

remember run cmd as Administrator

edited May 29, 2012 at 15:03

answered May 29, 2012 at 14:58

Zach dev

1,6208 silver badges15 bronze badges

4 Comments

rwbutler Over a year ago

Everything's set up correctly on these fronts, it's mainly the routing that's the issue I think.

Zach dev Over a year ago

but if routing problem, it should operate any url, suppose you're using the default routing map {controler}/{action} should operate the mysite.com/home/index

Zach dev Over a year ago

check out the user who runs the app pool has permissions

kenny Over a year ago

And if the 4.0 app pools are enabled.

rkralston · Accepted Answer · 2013-01-04 22:40:38Z

0

We had this same problem. The application works fine on the development machine. It works fine as the default application on the development server. Move the application to another site on the IIS server and we get 403 errors. We checked permissions - everything was fine.

We added the following to our _BaseLayout.cshtml:

<script>
        var SitePath = '@Url.Content("~")';
</script>

Each call in js and each anchor href have the SitePath prepended.

This makes the code work.

answered Jan 4, 2013 at 22:40

rkralston

3861 gold badge5 silver badges20 bronze badges

Collectives™ on Stack Overflow

Deploying a .NET MVC web application to a subdirectory in IIS

3 Answers 3

2 Comments

4 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related