Hi I would like to create a virtual directory at http://localhost
Its just a standard IIS 7.5 installation, meaning that http://localhost/ just shows the iis logo. But how do I remove that page and make it possible to use it for at virtual directory.
Right now Im getting this message in Visual Studio, when Im trying to create the virtual directory.
"Unable to create the virtual directory. The URL 'http://localhost/' is already mapped to a different folder location."
I can create a virtual directory at ex. http://localhost/web But I need it to be a http://localhost/
What you want is not a virtual directory. Just change the physical path of your Default Web Site to where you want it, or publish into that folder. By default the physical path is c:\inetpub\wwwroot\.
Default Web Site -> Manage Web Sites -> Advanced Settings -> Physical Path
Right click the folder that you want to make as the virtual directory.
Under Properties->Web Sharing select the Default website.
Also click the option Share this folder. In Aliases give the name of the folder. Now click OK.
There's nothing "virtual" about the directory mapped to http://localhost. That's your web root, likely located at c:\inetpub\wwwroot\. You should be able to publish directly to that.
A Virtual Directory is basically configuring IIS to internally create a folder under the web root which points to a different folder on the file system, as opposed to one actually located under the web root folder. It doesn't sound like you need that.
Related
I have a few files in certain SharePoint folders that I would like to access from a Windows (Virtual Machine) remote machine. As a test, I copied the "link" of a SharePoint Excel file and used it in the WindowsVM browser and I connected successfully and opened the file.
I also tried to map a SharePoint folder's "link" within WindowsVM Folder Explorer/Network but I am getting the below error msg
Is there a way to accomplish this?
Thank you
To be able to map a SharePoint site as a network drive (this uses WebDAV) please make sure:
The SharePoint site url is added to trusted sites list in Internet Option -> Security -> Trusted sites.
Use Internet Explorer to navigate to the SharePoint site and sign-in using your credentials and leave the browser open (this should not be required but it helps somehow)
Now try to map the site as a network drive.
If the above does not resolve the issue (and assuming you are running Windows 10) you can additionally navigate to Settings -> Accounts -> Add a work or school account.
Edit:
If you only have Edge browser (no IE) - you'll need to open the SharePoint site in IE compatibility mode on Edge and login-in (SharePoint looks ugly in this mode). Once this is done continue to map the drive.
I have installed url rewrite tool. I have set a global rule by right clicking on the server name (not a website name) and created a rule.
Now I want to edit this rule manually but I don't know where these settings are stored? when I create a rule for a website, it is stored in web.config but in this case I created rule for whole server and I can not find where it is stored? Is it stored as windows registry key? Do browsers look for windows registries rather than the web.config to ask for rules?
When doing a configuration via IIS Manager, the statusbar shows into which file the settings will be stored. At server level it mostly is applicationHost.config which is stored at %windir%\System32\inetsrv\config\applicationHost.config.
I have just added a new Win2012 IIS8 server to my website. The main part of the site is working fine, but I have a problem with a virtual directory. The physical path points to an IP address (\192.168...). The 'connect as' user is set correctly. 'Test Settings' reports no problems. The setup matches precisely other servers on my site (except that they are IIS 7).
The problem happens when I click 'Edit Permissions' for the virtual directory. Instead of seeing properties for the directory, I see properties for 'System32'. I cannot set permissions for the virtual directory, and so I can't serve files from it.
On another server, 'Edit Permissions' behaves properly. I can see the permissions assigned to users on the Linux box. If I 'Add' to add another user, the 'Location' box shows me the Linux server IP, and I can add a Linux account.
I can browse, view, and edit files though Windows Explorer on the Linux server, so there is no connectivity problem. But IIS doesn't see it.
I feel like I missed a step somewhere - any ideas out there?
Found the answer over on serverfault (which is probably where I should have posted in the first place...). The allowSubDirConfig value for the site needed to be set to 'false'.
Details here
I am hosting a modx website on ixwebhosting.com
After I submitted the site, I get this message when I try and access the root for example:
wwww.website.com/
or
www.website.com/manager/
I can get it to work, however, if I go directly to :
www.website.com/index.php
or
www.website.com/manager/index.php
ixwebhosting.com offers windows hosting
What do you think is causing this?
Right click on the virtual directory (gear icon) in IIS snapin, click Properties.
Check the box that says 'Directory browsing'
Click okay (and possibly?) restart IIS.
sounds like the default document setting is not "turned on" for the IIS
I have 3 web projects in a Visual studio solution.I want to create a single web setup project which should install all 3 web projects in their virtual directories.So how to create a single web setup project which supports multiple web application installation?
You can do this by creating a Web Setup Project. In the File System add as many Web Custom Folders as you need.
Only the main Web Application Folder will have the installation dialog so if you want to customize the virtual directory names then you will need to add a screen and set the Property of the web custom folder to be the same as the field name on the screen you add.
I never found the whole "web setup project" concept to work well. For starters, I've never managed a web server where the only site configuration was the default web site, so the "out of the box" functionality of defining a virtual directory to be created on the default site never worked for me, and it doesn't sound like it would be very useful to you either.
The best option I've found is to create a standard setup project that installs the output + content files of each web site into a \\Website path (or similar) and write a custom installer action with a supporting GUI that allows the installer (user) to select the proper web site and specify the name of the virtual directory to be used.
As John Hunter said, it is possible to add multiple Web Custom Foldsers beside the default Web Appplication Folder. But you need to know some details about how things add up.
One thing to notice is that the Property name you set for the additional folder will be the physical path of the installation. This however is read only in your setup logic, because it is automatically set later as the location of the IIS default path (typically C:\intepub\wwwroot\) added with the value specified in VirtualDirectory on the folder properties. So what you need to set in the custom screen you add, is not the Property name defined on the folder, but the property name that is used for the virtual directory. This is the Property name you specify appended with "VDIR". So if the property name you specify for the web folder is "WEBSITE1", then the property name for the virtual folder will be "WEBSITE1VDIR". In your custom screen, you then need to set up the property name for the text field you use to "WEBSITE1VDIR", The default value in this textbox will be automatically populated with you default VirtualDirectory value specified on the folder.
If you choose to remove the default Installation Address dialog so you specify also the main web site in a custom text box on the same page as the others, you need to know that the property name for the physical path as you see grayed out is fixed to "TARGETDIR" in the Property name for the "Web Application Folder". However, the property for the virtual path is not "TARGETDIRVDIR" as it would be if it followed the same name convention as the other, but it is "TARGETVDIR".
But if you do remove the default Installation Address dialog, you loose the option to select the web site to use (typically "Default Web Site") and Application pool from drop downs that shows you what is available.