I have an existing deployed ASP.NET MVC3 application using Entity Framework 4.1 and .NET 4 that I need to copy to a new server. The problem is that I have little or no documentation on setting up a deployed environment. At the top, I make the administrator access to the deployment environment and full access to the application source code.
So, starting with bare metal, I have:
- New installation of Windows Server 2012, SQL Server 2014 Enterprise
- Installed MVC 3 and tools through the web platform installer
- The whole website copied from the existing deployment to its folder under C: \ inetpub
- A site was added to IIS and started with an application pool configured as
- Go to the site and return the default.htm page to the root folder. This is not the expected behavior, as it should serve the default view of the controller.
- Make sure that I can access the html file elsewhere on the website, for example. http : //myhost.com-00-0043/SomeDir/test.htm and he serves this.
- See if he gets into a route that I know, for example. http : //myhost.com-00-0043/Auth/NewLogin and I get
- Various indications show that sometimes it is caused by the fact that "UrlRoutingModule-4.0" is not installed in the modules. This was not so, I added the same server and ensured its presence on the website (did not make a difference):
- There is also a mention that runAllManagedModulesForAllRequests = "true" was present in the web.config file, which is located
UPDATE
Set
.NET:
So, before posting the “Failed Trace Request”, can anyone give me any suggestions on how I can get MVC to work in this environment?
I read SO and Googled posts, but nothing works.
iis asp.net-mvc-3
Theedge
source share