My production environment have a root, and my virtual directory will be at /brazil folder inside the root.
When I convert my website project(not web application), that works correctly with Cassini at /brazil since my website folder is brazil, IIS Express put the site at root, how can I change this?
I'm seeing similar problems with IIS Express with web applications. From what I'm seeing, IIS Express actually allows you to define a folder in the 'Project Url' field, but then when launching it generates 2 websites, one with the folder and another for the root application. Problem with this is that it is using the same folder for both which brings web.config inheritance issues.
My solution was to go edit the hosting file and change the physicalPath for the root virtual directory to an empty folder in my system
For example:
<site name="MySite1" id="1">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\VisualStudioProjects\2010\MySite1\MySite1" />
</application>
<application path="/ssd">
<virtualDirectory path="/" physicalPath="C:\VisualStudioProjects\2010\MySite1\MySite1" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:59473:localhost" />
<binding protocol="https" bindingInformation="*:44302:localhost" />
</bindings>
</site>
To this:
<site name="MySite1" id="1">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\TEMP\New folder" />
</application>
<application path="/ssd">
<virtualDirectory path="/" physicalPath="C:\VisualStudioProjects\2010\MySite1\MySite1" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:59473:localhost" />
<binding protocol="https" bindingInformation="*:44302:localhost" />
</bindings>
</site>
Related
I have a Azure site and have create a Virtual applications under the site:
xxx.yyy.com/test
I deploy my ASP.NET application into this directory.
But how can I have the same setup when I do debug in Visual Studio. When I hit F5 would I like to have the application "deployed" and run in localhost:5000/test, and not localhost:5000.
Why is it that you find the answer 2 sec after you post a question?
Open the applicationhost.config for the solution, it is hidden in the .vs folder.
Find the application tag. Copy and add a new application tag and change the path from / to /test. On the first application tag did I change the physicalPath to something else.
<site name="xxx.yyy" id="2">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="D:\" />
</application>
<application path="/test" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="D:\Project\xxx\src\xx.yy" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:5001:localhost" />
</bindings>
</site>
I have a WebSite (not project, WebSite) using ASP.NET Webforms, at the begining this WebSite was created using Casini (old visual studio Web Server) with "GestorAplicaciones" as virtual directory.
The start url for the application was "http://server:port/GestorAplicaciones/Default.aspx"
Now I have opened this web site on Visual Studio 2013 and running under IISExpress but I had problems with virtual directory.
My web site in applicationhost.config was:
<site name="GestorAplicaciones" id="12">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\...\GestorAplicaciones" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:10000:localhost" />
</bindings>
</site>
Searching for information about the problem I found how to create a virtual directory in IISExpress, I have to do this:
<site name="GestorAplicaciones" id="12">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\Temp" />
</application>
<application path="/GestorAplicaciones" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\...\GestorAplicaciones" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:10000:localhost" />
</bindings>
</site>
This way my web site work fine with virtual directory.
However each time visual studio open the solution it change the configuration of the website in applicationhost.config, it write this again:
<site name="GestorAplicaciones" id="12">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\...\GestorAplicaciones" />
</application>
<application path="/GestorAplicaciones" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\...\GestorAplicaciones" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:10000:localhost" />
</bindings>
</site>
Then the website doesn't work and I have to change applicationhost.config each time open the solution in Visual Studio.
How to do to visual studio don't change my web site config in IIS Express??
I'm developing a Web API using VS2012. In order to allow my mates access the api in the same LAN, I need to modify the applicationhost.config file.
The problem is that sometimes when I modify the code and start debugging, I found that IIS Express created a copy of my application, say MyWebAPI(1), MyWebAPI(2)... Then I have to modify the applicationhost.config again.
Does anyone know in which case IIS Express will create a copy of my application?
Here is an example of what my applicationhost.config:
<site name="MyWebAPI(1)" id="15">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\Example\example" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:8080:*" />
</bindings>
</site>
<site name="SunPower(2)" id="16">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="C:\Example\example" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:8080:*" />
</bindings>
</site>
In my solution, I have 2 projects, call them Foo and Bar. When deployed, Foo is the root site (http://mycompany.com) and Bar is a sub-directory (http://mycompany.com/sub).
When I work on them locally in IIS Express on my local machine, I need to replicate things into web.config of both projects since I work on them separately. For example, I have one of the HMTL5 Boilerplate rules for "cache busting" in my Rewrite rules:
<rewrite>
<rules>
<rule name="Cachebusting">
<match url="^(.+)\.\d+(\.(js|css|png|jpg|gif)$)" />
<action type="Rewrite" url="{R:1}{R:2}" />
</rule>
</rules>
</rewrite>
If I just leave it in the web.config for Foo, then when I work on Bar, it's not applied and I get errors since the rewrite isn't happening. So I've replicated sections into the web.config for both projects.
But when I publish the solution to Azure, I get conflicts because of the inheritance rules since the web.config for Foo is in the root.
What is the best way to manage this? I tried to search on this topic but couldn't find this exact problem described.
Update:
My applicationhost.config for IIS Express is as such:
<site name="Bar" id="3">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="E:\Code\mycompany\Bar\Bar" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:65052:localhost" />
</bindings>
</site>
<site name="Foo" id="4">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="E:\Code\mycompany\foo" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:50477:localhost" />
</bindings>
</site>
I tried editing it to make both apps part of the same site, with these changes but no luck. Seems to have broken everything :)
<site name="Foo" id="3">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="E:\Code\mycompany\foo" />
</application>
<application path="/Sub" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="E:\Code\mycompany\Bar\Bar" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:65052:localhost" />
</bindings>
</site>
Make your root site (http://mycompany.com) as a website in IIS, and your sub-directory as virtual directory in IIS.
IIS shares the Rules defined in root website ('s web.config) with the virtual directory.
Use web.debug.config and web.Release.config to manage the development and release environment difference. For more please follow this SO POST or this MSDN blog
I'm building an ASP.NET 3.5 web application. When I run the project (using Visual Studio's built-in server), it needs to be able to access a network share as a virtual directory. I can't seem to find any information about how to do this.
The network resource is very large, is updated frequently, and is used by other developers and in other projects projects--not just me and mine.
I understand that I can create an IIS virtual directory to the network path once the site is deployed, but that doesn't help me while I'm debugging.
You can't do this with the web development server. It's for debugging a single application, not one that depends on multiple virtual directories.
How does it reference the virtual directory mapped to the share? By redirecting to resources under that virtual directory? If so, then during debugging, could you just change the location it redirects to to be an IIS virtual directory?
It's now possible to have both virtual directories and sub-applications with newer versions of Visual Studio and IIS Express.
Open .vs\All\config\applicationhost.config in your text editor of choice, then navigate to the configuration/system.applicationHost/sites node.
Update the site element that corresponds to your parent application, like so:
Original:
<site name="Web" id="1">
<!-- parent application -->
<application path="/" applicationPool="Clr4IntegratedAppPool">
<!-- application root -->
<virtualDirectory path="/" physicalPath="C:\Src\Web" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:5706:localhost" />
<binding protocol="https" bindingInformation="*:44300:localhost" />
</bindings>
</site>
Modified:
<site name="Web" id="1">
<!-- parent application -->
<application path="/" applicationPool="Clr4IntegratedAppPool">
<!-- application root -->
<virtualDirectory path="/" physicalPath="C:\Src\Web" />
<!-- virtual directory -->
<virtualDirectory path="/DocRoot" physicalPath="C:\Src\DocRoot" />
</application>
<!-- sub-application -->
<application path="/FooBar" applicationPool="Clr4IntegratedAppPool">
<!-- application root -->
<virtualDirectory path="/" physicalPath="C:\Src\Foo Bar" />
<!-- virtual directory; shared with parent app, so must be duplicated -->
<virtualDirectory path="/DocRoot" physicalPath="C:\Src\DocRoot" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:5706:localhost" />
<binding protocol="https" bindingInformation="*:44300:localhost" />
</bindings>
</site>
Save and restart IIS Express.