In IIS 5.1, I set up a website to point to my ASP.NET MVC project project, and I get a "Service Unavailable" error message when I try to access it after creating a project. It seems that I should publish the site in a separate directory and point IIS to the published version to make it work.
I already tried " aspnet_regiis", but this does not fix the problem. I also configure wildcard matching, so all requests are sent through the ASP.NET pipeline.
I'm not sure why I need to publish files to view them. In the published version, apparently, only unnecessary files are deleted, but the published files seem to be identical to those in the actual project directory.
Need to publish your ASP.NET MVC website to a different directory so that IIS can serve it?
Ideally, I would like to configure it in such a way that all I need to do is build a project, and I can immediately view the updated website by visiting localhost.
Update:
The version is set to 2.0, and when I get home I will check if the account has IUSRsufficient privileges. I can’t imagine why this is not so, because the published folder apparently had them by default.
Update # 2:
Errors in the event log:
AppDomain:/LM/W3SVC/1/Root
: System.IO.FileLoadException
: "System.Web, Version = 2.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a" . .
, ASP.NET . : 0x80070005 .
MY_MACHINE\ASPNET " ", .
№ 3:
, ... XP Media Center Edition, , .
, . , , ASPNET. "" (, , ) .
# 4:
, , , . , ASPNET .
ASPNET .