I searched alot among tutorials but I'm so confused now.
I Created an ASP.MVC3 application with VS2010 named tile-shop2,
installed IIS7,
in IIS7 manager in Default Web Site section created a new app named tile-shop2 with ASP.NET V4.0 Application pool, and Physical path is the place that application is created (document, Visual Studio 2010, Projects, ...)
in VS2010, right clicked on the name of project and clicked Publish,
in VS2010 in Project menu => tile-shop2 properties => Web => Servers => ticked Use Local IIS Web server
when I run VS I see this window:
and when in browser searched localhost/tile-shop2 I see list of directoris in Solution Explorer, and when I click on one of them, Error 404.8 appears.
(I run aspnet_regiis and IIS7 works itself)
Can anybody please tell me what is wrong here?
Thanks so much
It sounds like the IIS application is pointing to the folder containing your web project and not the published web project contents.
You want to create a folder within your IIS root ('C:\inetpub\MyProject') and point your IIS application's physical path to this same publish folder, rather than your Visual Studio project folder. You then need to publish the website to this folder using Visual Studio.
Related
I developed an asp.net mvc 5 web application using VS 2015 community edition. All things worked perfectly, but a few days ago, Visual studio was unable to load the web project, and the below error message is displayed :
error : The Web Application Project elab is configured to use IIS. To access local IIS Web sites, you must run Visual Studio in the context of an administrator account. In addition, you must install the following IIS components: ASP.NET
I tried to run VS as "Administrator" but unfortunately due to our organisation security policy, I don't have this privileges.
Is there a way to overcome of this problem ?
You can try the below solution
In the solution explorer, right click on the project and select "Properties"
Click on "Web" tab
Select "Use Visual studio development Server" radio button
The above steps will help you to Switch from local IIS to IIS Express ie Visual studio development Server
Note : In the same way you can switch back to use local iis at any time you want, but that requires an administration privilege
I am new to MVC applications. I would like to host my MVC6 application on shared windows platform (hosting package). I have uploaded my project files via FTP onto the domain I created with my service provider. My project has a solution file (.sln) which point to my application and But unfortunately, the hosting platform requires my application to have a default.aspx file in order for it to be viewable online. Because of this I am unable to view the application online. How do I create a default.aspx file or get my application to show online?
Use Visual Studio one-click publish. In Solution Explorer, right-click your project then select Publish.
Case your code is correct, you should see your web application.
I am using Windows 10 and Visual Studio 2015 community. I am having trouble finding my ASP.NET MVC sites in my IIS Manager after I create the virtual directory in the Properties window.
I originally was unable to view the IIS manager on my Windows 10 and had to search for "Windows Features" or "Turn Windows Features On or Off". I then selected the "Internet Information Services" checkbox.
I want to be able to host the site such that when I open it up from IIS Manager it should show up under the default web sites.
In the tutorial he was able to make the app do this by going to the Project's properties, the windows tab and check the Local IIS selection as below:
enter image description here
Unfortunately I don't have his version of visual studio and all I see is:
enter image description here
When I try to create the virtual directory anyway it doesn't show up in the IIS Manager. What do I do?
The tutorial that you are following is of Visual Studio 2012 or prior as it is giving you development server option.
In your current version on the project properties => web screen there is a Servers section in that you can see a drop down that has value IISEXPRESS . Change it to Local IIS , Click on Create Virtual Directory next to it and this will create an application in your local IIS under the default web site (which ever is on port 80)) which you can see using IIS manager.
Make sure you are running visual studio in Administrator mode
I faced the same problem with the visual studio 2017 . Right click the VS tab and open it in admin mode , and it will show the option of local host under server dropdown.
is there anything special I need to do to get ASP.NET MVC3 enabled on my Windows 8 Release Preview install? Creating even a blank ASP.Net MVC3 Razor application in VS2010, deploying to the local IIS instance as a new application, and loading the page in the browser doesn't work. I'm met with the following error:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
So I've then gone in to the new VS2010 project, right click, select "Add Deployable Dependencies" and selected "ASP.NET MVC" along with "ASP.NET Web Page with Razor syntax"
Then I re-deploy the project to local IIS application. No change. Still "web server not configured to list contents of the directory".
It's worth noting the VS 2010 Development Web Server works fine.
Any ideas?
Found it. Turns out even though I'm using ASP.NET MVC3 and had the .Net 4.0 framework installed, the Windows 8 "feature" for ASP.NET 4.5 needed to be installed for all this to wire up. Seems a bit counter-intuitive, but changing that did it.
You may want to consider running the MVC3 installer on your host machine so that all dependencies for MVC3 projects are stored in the GAC. If you need the install package you can download it from:
http://www.microsoft.com/web/gallery/install.aspx?appid=MVC3
I can't verify that this works on the Windows 8 preview, but it would be my first instinct upon running into your problem.
Did you ensure that the worker process for the site is configured for .NET 4?
When you say you "Deployed", how did you do that? It sounds like the folder is not being set to an application.
For me .NET 3.5 was not installed for IIS 8 in Windows features. Although I'm pretty sure my app is .NET 4.0... Worth trying though.
I had problems installing MVC3 MS VS 2010. Windows 8 x64. The platform installer shows no errors.
Root cause : aspnetwebpages.msi breaks updating web.config files. I updated two web.config files which appeared to only contain blanks.
Here are my directions:
Ensure C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\web.config is valid. Use web.config.default, copy then rename to web.config to correct if it looks wrong.
Ensure C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\web.config is valid. Use web.config.default, copy then rename to web.config to correct if it looks wrong.
I don't know why the files were bad in the first place.
I have a Visual Studio 2010 Solution that contains a few library projectes, a few WPF projects and an ASP.NET MVC 3 project. When i start any project the MVC project get started in the development-server.
Is there some way to stop this behaviour?
Edit:
I just checked to make sure I´m to doing too much wrong. If you start a new solution with a console/whatever project and add an mvc3 project, everytime you start the console project the mvc project gets started as well.
Not sure if this is buggy or an intended feature, but it is kind of strange that the behaviour is so different from normal projects.
If you don't need MVC project for certain period of time, you can unload it (Right-click on the project and select Unload project).
Another option is to select local IIS as a web server (If you have it installed). This way it won't start development server.
You can always choose another project as the default project to start up. You can right-click on the project and set as startup project.
Make sure all your web projects are set to use local IIS rather than the Visual Studio Development server. Unlike the development server, IIS doesn't do anything with a new build until you actually try to load a page.