Install Multi .Net applications onto IIS

[dvannoy]

I posted this in the IIS forum but it doesn't look like there getting much action there so I'll post here also.

I have installed an asp.net application onto the

http://wwwroot

that controls my portal environment. I then created a web application under the default website that contains it's own web.config, app files etc. once I try and call that application it seems like IIS is pointing to the web.config file on the root not where that application is stored. how can I have multi web applications running on one IIS server?

any help would be appreciated

thanks

 

[tperri]

have you tried using virutal directories for your applications? This is how I have multiple apps running on windows server 2003.

 

[ca8msm]

Yes, if this is a sub folder within the main folder, it will pick up some values from the main folder. If you setup a virtual directory for the sub folder this should not happen.


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[dvannoy]

so just set it up as a virtual directory and remove it as an application? is that what your saying?

what I did was first create a virtual directory and then inside the properties for that virtual directory an application gets created.

 

[ca8msm]

No, what I meant is the steps you have just described.

When you say "it seems like IIS is pointing to the web.config file on the root not where that application is stored", how are you coming to this conclusion?


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[dvannoy]

OK, I got it..now I'm getting these errors.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>