I am trying to publish an MVC 2 application to my local Win 7 IIS 7.
The app pool is Integrated 2.0, not classic.
The app is .net 3.5.
The project was originally started in VS2008, but I have upgraded to 2010.
I publish the app through the VS wizard to a file location, I have also tried publishing again in VS, but web deploy to localhost - neither makes a difference.
The app spins up fine when I just hit F5 in VS and work in debug mode.
Any ideas? I have googled about, but nothing has sorted it.
Thanks in advance.
Did you make sure the AppPool is set to allow 32bit apps?
Related
I created a brand new ASP.NET Core Web App project to test out the new features of .NET 6.0.
But when I tried to run the application with F5 nothing displayed on the web browser but "Page Not Found" error.
Also I tried with IIS Express and the result is same. Also tried http and it's same.
I don't have any idea what may be the problem?
After I rebooted my computer project runs well.
But sometimes later problem occurred again. I tried changing ports, rebooting, close and relaunch visual studio. None of them solved the problem.
Must be a computer specific problem but don't have any idea where to start. Really annoying.
So I keep searching and trying, I came up with this solution:
ASP.NET Core 404 Error on IIS 10
dotnet restore
dotnet run
It works for now but the problem related to debugging still persists.
I am running VS2012 (Ultimate version 11.0.51106.01 Update 01) and do have a website project along with some console, WPF and WCF server projects. My normal debugging runs a non website project and rarely do I debug the website project.
Any debugging however, always starts IIS Express. How can I prevent that? The website project "Web" tab forces me to select some web server and "IIS Express" is currently selected, but I don't want it to start unless I'm debugging the website. Seems like this started happening after some recent VS2012 maintenance as I don't remember it happening before about a few weeks ago. Now getting old.
Is this a VS2012 bug that any debugging fires up IIS Express?
Anyway to not start it when I debug a WPF or console app?
I just converted an app from VS2008 to VS2010. But when I try to view the site in IE I get the message "Internet Explorer cannot display the webpage". This same app worked perfectly when I published the VS2008 version to the same folder. Any ideas?
The app uses .NET 4.0 which requires an IIS 7 App Pool using .Net 4, not 2. When I created a .Net 4 App Pool and assigned it to the app website the problem was resolved.
Is there some kind of deployment wizard I can run and have it install just the things it needs to run right onto the server end point? Do I have to build the project using VS2010 on the server? If I can't get this thing deployed today I am really going to be screwed.
IIS 6 is there and I think .NET 4 is installed (I tried installing it from Microsoft and they had me install a million things like VS2010 express and SQL Server and all this other crap, the install failed but .NET 4 does show up in IIS).
I achieved this by enabling an FTP site for the IIS server website and using this to deploy the web application within visual studio 2010 which will build and deploy just the changed files for each build. Works very well. You can even add a Publish toolbar to help deploy regularly more easily.
All you have to do is install the .NET Framework 4.0 (32 / 64 depending on build) and run aspnet_regiis.exe in the Framework folder.
For me this is located here:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe
Hope this helps!
You can also use the publish command from VS 2010 to save it to the filesystem and then copy the files into an IIS site on the target server. Just map a network drive to X: or something (for your sites root) and publish directly to the share.
You can take a look at Web Deployment projects or even the VS "Publish" feature
From the Build menu in VS2010, just click Publish [name of your web project] and enter the location on your web server where the site is going to be hosted.
VS2010 will publish the files required there.
It shouldn't be necessary to install VS2010 Express, just to deploy a site. But if .Net 4 and ASP.NET MVC 3 is installed, you should be able to deploy. Right click the web app in VS2010, and hit Publish.
Remember to set the configuration to Release!
But, with IIS 6 you could be in for a fight in regard to HTTP Modules, Handlers and other server configuration. Anything inside your Web.config's system.webServer section will always be ignored by IIS 6.
I have recently started to received this message.
Unable to start debugging on the web server.
The IIS worker process for the launched URL is not currently running
Does anyone know what this means?
I created my virtual directory via Properties on the project, and clicking Create Virtual Directory. ANd in IIS I can see it, I run VS 2010 with Admin Privs.
The Application pool in .Net 4.0
Any help really appreciated
Thanks
EDIT
I managed to get it working but its a good workaround really. Basically there was another website setup i.e. Default Website where all my apps goes which was started and running.
And there was another website (which was stopped!) that was for installanywhere.. But it was stopped! ... I removed the site completely and now it works
Can vs 2010 not figure out which one to connect to or something?
I presumed if its stopped then it wouldn't try and connect..
Very confused, Anybody know of alternative work around?
I got the same error message after reinstalling VS2010. In my case all application pools in the IIS where remapped to run 4.0, so VS2010 was unable to figure out which pool to attach its self to during debugging. The solution in my case, was to manually delete few pools and remapping my older pools back to .net 2.0. I finally ended up, only having 2 pools pointing towards .net 4.0 (integrated and classic) and 2 pools running .net 2.0 (integrated and classic).