I think I must have changed something to IIS default website settings. Now I cannot even browse IIS default website. Even if I create new website, when I browse, it always go to http://localhost/webpages/home.aspx which became the default page for all website I added to IIS. where can I change that setting not to call that http://localhost/webpages/home.aspx by default.
any pointer would be appreciated.
if I understand your question correctly.
These steps should help you to produce the result(s) you require:
1 Create your project in VS.
2 Right click Project name.
3 Select Properties.
4 Select Web.
5 Under Server there is a dropdownbox. Here the default is IIS.
dropdownbox
The usual choice as far as I know is between IIS and localhost.
6 Click the Create Virtual Directory button located to the right.
A message box should pop up saying Virtual Directory successfully created!
Here is a link that may be more helpful. https://www.youtube.com/watch?v=k5RKfOEpOGk&index=9&list=PL6n9fhu94yhXQS_p1i-HLIftB9Y7Vnxlo
Related
How do I set up IIS to debug classic ASP?
Help Needed Setting up Classic ASP Debugging
According to what I have seen on social media, in order for me to set up my computer for writing and debugging Classic ASP, I need to set up IIS a certain way -- which I did -- and then I have to enable ASP by doing the following:
IIS7 - IIS > ASP > Compilation > Debugging Properties > Enable Server-side Debugging
And I am stuck on this. Please, someone give me an idea of what I need to click on.
The steps to implement your requirements can be found easily from internet. The reason why you can't see "ASP" module in your screenshot is you didn't enable "ASP" feature. Please refer to the steps below:
1. Open your "Control Panel" --> "Programs" --> "Turn Windows feature on or off".
2. Then you can find "ASP" option under "Internet Information Services" --> "World Wide Web Services" --> "Application Development Features" like below screenshot.
3. Just enable "ASP" and then go to your IIS manager, choose the site which you want to edit under "Sites". Then you can find "ASP" module.
Hury Shen posted a very good answer. I might be ready now to have a go at making my first "Hello World" classic ASP program.
The answer provides content that even the online Microsoft Documentation I have read has left off. Namely, it is checking the ASP box.
I clicked on the help button and this lead me to a browser page which explained how to create an ASP page.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831768(v=ws.11)?redirectedfrom=MSDN
This link offers this help:
and this takes me to a new page
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831387(v=ws.11)
I have accomplished the prerequisite and step 1 on the list. So I go to step 2
Step 2: Add a Classic ASP Website You can perform this procedure by
using the user interface (UI), by running Appcmd.exe commands in a
command-line window, by editing configuration files directly, or by
writing WMI scripts. To add a website by using the UI Open IIS
Manager. For Windows Server 2012, on the Start page click the Server
Manager tile, and then click OK. On the Server Manager Dashboard,
click the Tools menu, and then click Internet Information Services
(IIS) Manager. For Windows 8, on the Start page type Control Panel,
and then click the Control Panel icon in the search results. On the
Control Panel screen, click System and Security, click Administrative
Tools, and then click Internet Information Services (IIS) Manager. In
the Connections pane, right-click the Sites node in the tree, and then
click Add Website. In the Add Website dialog box, type a friendly name
for your website in the Site name box. If you want to select a
different application pool than the one listed in the Application Pool
box, click Select. In the Select Application Pool dialog box, select
an application pool from the Application Pool list and then click OK.
In the Physical path box, type the physical path of the Web site's
folder, or click the browse button (...) to navigate the file system
to find the folder. If the physical path that you entered in step 5 is
to a remote share, click Connect as to specify credentials that have
permission to access the path. If you do not use specific credentials,
select the Application user (pass-through authentication) option in
the Connect As dialog box. Select the protocol for the Web site from
the Type list. The default value in the IP address box is All
Unassigned. If you must specify a static IP address for the Web site,
type the IP address in the IP address box. Type a port number in the
Port text box. Optionally, type a host header name for the Web site in
the Host Header box. If you do not have to make any changes to the
site, and you want the Web site to be immediately available, select
the Start Web site immediately check box. Click OK.
It has been a long time since I have done anything like this. Basically, I assume I am turning my desktop computer into a web server. Am I right? If this is so, do I have to follow through with all the overhead and steps in buying a namespace? I hope not.
I have questions about step 4 : "If you want to select a different application pool than the one listed in the Application Pool box, click Select. In the Select Application Pool dialog box, select an application pool from the Application Pool list and then click OK." As I type out the site name, the field for "Application pool" repeats what I type for the site name. Since I am not creating a new application pool -- or I do not want to -- I click on select and choose the DefaultAppPool .
Since I am only wanting to write test code locally, I connect as an application user.
I did not put in an IP address.
It complained that I was using port 80. So I switched it to port 79 and clicked ok.
So now I think I have an asp website. What do you think?
The title is purposely generic as I have no clue to formulate my question in any different way.
I have made an MVC 5 project using .NET 4.7.
My goal is to use IIS 10 to point to a domain so I can use that as a testing ground.
I have already edited my host-file to point my localhost ip to the domain I have in mind.
After that I have followed every step mentioned in the video below meticulously.
However I keep ending up on the 403.14 error page.
I have adjusted security to no avail, checked the app-pool to use the correct .net version... I'm all out off ideas.
https://www.youtube.com/watch?v=IwbKquNBNgQ
I hope someone here has some idea of things I have not thought of myself, so feel free to ask anything you think might make the change I need to make this work. I will edit this message (and title) as much as needed to keep up to date as possible.
EDIT: I have followed the full guide that I have marked as an answer. I had 3 differences.
Difference 1 was in Windows Features. I think I just plain didn't correctly mark all the needed features..
Difference 2 was in Security. I did not have IIS_IUSRS added, only IUSR
Difference 3 is one I have purposely keep a difference and that is Directory Browsing. Without this being enabled, it works for me.
I hope that if anyone ends up on this page in the future, the answer provided below will be as helpful as it has been to me.
make sure you enabled below iis features:
please follow the below steps to publish your MVC project in iis.
1)open the visual studio. Select your site and right-click on that-> Click publish.
2)in pick up publish target Select folder option and create choose destination where you want to publish the site. (make a new folder and publish a site in that folder) and then select publish.
3)open IIS manager.
4)expand the server name and right-click on sites and select add a new site.
5)enter the site name, physical path, and site binding details.
ip address: select your machine ip address.
port: 80
domain name: your domain name
6)make sure you enabled directory browsing in iis.
7) The application pool is running under application pool identity, a version is correct and using the integrated pipeline.
8)anonymous authentication is enabled.
9)iis_iusrs and iusr have full permission to access the site folder.
host file enry:
bind your machine IP dress with a hostname of the site.
after doing all the changes refresh the site in iis and browse.
So, I did something and my localhost website gave me a 500 error. Couldn't figure it out so I figured I'll delete the website in IIS and then re-add it. Apparently that was a mistake. I can't see the added website locally anymore. I seem to recall having to add a permission or something to be able to view it in localhost but for the life of me I don't remember what setting that was and I can't find it online. Any ideas? My other local website still displays fine ... Using Windows 8 IIS 8.5
I'm simply going to Add Website > putting in the site name and changing the port number. I've left the IP address alone to All Unassigned (I just want to view in as localhost:24)
Adding website in IIS:
1. Right Click the Sites Folder image.
2. Add website.
3. Enter Site name.
4. On physical path textbo, Locate where do you want to store your website.
5.Assign a port.
then done.
After creating.
1. Select website created.
2. Open Directory Browsing.
3. On the right side click disable.
Make sure in application pool that your website has same framework set up.
A developer just send me a running website files from IIS directory. I want to know if I can run the website on my PC. The file contain "Default.aspx" file, which I assume is of some importance.
I want to know if it is possible to run the website on my PC, I have installed IIS and I placed the file in the wwwroot folder, but unfortunately I dont know how to proceed from here.
Can someone please point me to the right way to continue with this task.
Thanks in advance
First time use of IIS
Now that IIS is running on your system, it should have defaulted to running on port 80. You can test this out by going to http://localhost/
The file you have placed in the wwwroot directory Default.aspx is an ASP.NET application. You need to go to IIS and convert the directory it is stored into a web application.
Now when creating web applications, it is better to create them in another folder other than your wwwroot folder, and in the case of this tutorial it is easier. Move your Default.aspx into a folder named 'webapp', or something of the like.
To convert it into an application, do the following:
In the Server Manager, expand the
'Roles' item in the tree
Expand the 'Web Server (IIS)' item
Click on 'Internet Information Services (IIS) Manager
In the window on the right hand side, you will need to open up your server. In my case, my server is called WIN2008R2. Your server name will be located inside the 'Connections' pane. Expand your server in the tree
Expand the 'Sites' item
Expand your newly created site. There should only be one there, and the item will have a globe next to it
Now right click on your 'webapp' item which will have a folder next to it, and click 'Convert to Application'. Then leave all the properties the same in the window that comes up and click OK.
You have now created a new web application. By going to http://localhost/webapp you should see it working.
You need to configure IIS to host an ASP.NET website.
You can find information about configuring IIS here: http://msdn.microsoft.com/en-us/library/ms178477.aspx
Another option is using the Cassini web server (instead of IIS). You may find it easier to configure: http://ultidev.com/products/cassini/
I wonder what the best approach is for a situation where I want to have the user type in
http://myserver/something/20
and get redirected (301 or 302) to
http://someotherserver/applications/something/modules/default.aspx?id=20
For .net 3.5 and IIS 7 I found some solutions, but unfortunately I am stuck with .net 3.0 and IIS 6.0 on Windows 2003, and I do not want to install anything on the server if possible. I can change the settings for the Virtual Directory though, and if I have to for the entire site.
HTTPModules and web.config are ASP.net only If I am not completely mistaken, hence that will not help as /20 is not sent to ASP.net per Default?
Can anyone give me some tips where I can set up something like that?
The only way I have seen to do it without putting the 301 redirects directly into IIS Manager is to use Wildcard mapping
Link
Map the .* extension to the same DLL as .aspx in the virtual directory's file mappings in Application Configuration. Then in the web.config's httpHandlers section, map the URL to the type.
You might enlist the assistance of ASP.
Create a 404.asp file in your something folder with the content:-
<%
Dim id : id = CLng(Mid(Request.QueryString, InStrRev(Request.QueryString, "/")+1))
Response.Redirect "http://someotherserver/applications/something/modules/default.aspx? id=" & id
%>
In Custom errors of the something folder in IIS manager tweak to URL and /something/404.asp
Note the querystring value passed to the 404 customer error page looks like:-
404;http://myserver:80/something/20
Edit: D'oh or you could use a 404.ashx custom error page and then use more familiar .NET code.
In IIS, right click on the Virtual Directory, select Properties.
Under the Directory tab, click the Configuration... button.
Under the Mappings tab, under the Wildcard application maps (order of implementation): click the Insert... button.
Browse and select C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll, leave Verify that the file exists unchecked.
Move Up aspnet_isapi.dll to the top of the list.
Click Ok, Ok, and try it. Try recycling the application pool if you don't see it work.
We had a situation where the .Net Routing was working on our development PCs but not on the test and production server with IIS 6 and Windows 2003. This fixed our problem.