Asp.Net Version error after deploying to IIS 7 - asp.net

I have developed my Application in asp.net 4.0 and I want to run it on localhost.
So I deployed my project in IIS but after deploying when I went to change Application pool from 2.0 to 4.0 I didn't find version 4.0 in application pool.
So I went to following path to check that Asp.net 4.0 version available or not.
C:\WINDOWS\Microsoft.NET\Framework\
But I didn't find version 4.0, Only version 2.0 Available.
I have done following things to run my application on localhost
Installed Windows 7
Installed IIS (with full features)
Deployed successfully my project to IIS
What I am missing here ?
Please help guys....

I would suggest starting at installing .NET 4.0.
https://www.microsoft.com/en-us/download/details.aspx?id=17851
Let us know if that helps.

Related

Publish a .Net 5.0 web in IIS from Visual Studio 2019 doesn't start

I am trying to publish a test website in .Net 5.0 on an IIS on Windows 10.
I have .Net 5.0 installed
I have activated the IIS on Windows
I have installed the ASP.NET Core 5.0 Runtime (v5.0.1)
I have installed the dotnet-hosting-5.0.1-win
I have created the web application in the IIS and assigned it a specific Pool with the .Net CLR version "No code managed" and "Integrated". I have assigned the port 8090.
From Visual Studio when Publish I selected:
File System
Configuration: Release
Target Framework: 5.0
Deployment Mode: Self-Contained
Target Runtime: win-x86 (with win-x64 it doesn't work either)
My Windows version is 1909 (OS compilation 18363.1256)
If I navigate to the path http://localhost:8090/ I get this error "HTTP Error 500.32 - Failed to load .NET Core host.
I have reset the IIS, I have deleted and recreated the application, I have restarted Windows, but it still does not start the test web.
The Windows event viewer showed me these errors:
Unable to load 'C:\inetpub\wwwroot\TestNetCore.\hostfxr.dll'. This might be caused by a bitness mismatch between IIS application pool and published application.
Could not find 'aspnetcorev2_inprocess.dll'. Exception message:
Failed to start application '/LM/W3SVC/2/ROOT', ErrorCode '0x800700c1'.
I don't know what else to look at. Any ideas or suggestions?
Your errors are in ASP.NET Core, For these errors, you can try the following solutions:
Have you install asp.net core module? if not, please install it:
ASP.NET Core Module
Open IIS manager > Application Pool > Select App pool > Advanced
Settings, update "Enable 32 bits applications" from false to true > Click OK.
Try to delete the applicationhost.config (in .vs\config\applicationHost.config) and rebuild app.
I solve this problem in this way for myself:
In web.config I remove hostingModel="inprocess"
I answer for others who encounter this problem

ASP.NET MVC Method not found: 'System.Version System.Web.HttpRuntime.get_IISVersion()'

I have an MVC site using Entity Framework 5.0 running on an IIS 7.5 web server. The site works well on my local machine, but when I upload it to the webserver I get the error:
Method not found: 'System.Version System.Web.HttpRuntime.get_IISVersion()'.
The site is running on its own integrated pipeline and I have other MVC sites running on the server without a problem.
Any ideas?
This was fixed with a reinstall of the asp.net 4.5 framework.
You must register the .NET Framework version after the installation.
1) Open a cmd window as Admin and go to the Framework v4.5 installation dir in your server and execute aspnet_regiis.exe -r
c:\Windows\Microsoft.NET\{Framework}\v4.5 /*The default folder is something like this*/
2) Go to the IIS and then change the .NET version from the current Pool where the Application is hosted.

Can I run an ASP.NET 3.5 application on a server with ASP.NET 4.0 installed without any problems?

Can I run an ASP.NET 3.5 application on a server with ASP.NET 4.0 installed without any problems? I am hosting a large number of website on a Godaddy server with ASP.Net 2.0/3.0/3.5 installed. However, my newest application needs 4.0 to run. If I upgrade the server to 4.0, will all my other sites break?
Your 4.0 application needs it's own 4.0 application pool. No, your other sites won't break. You aren't really "upgrading" the server, you are just installing the 4.0 framework.

Deploying .NET 4.5 web app with Web Deploy

I have a working ASP.NET MVC 3 application. The project is built with VS 2010 and targets .NET 4.0. Now I re-targeted it to .NET 4.5 and successfully recompiled. Trying to deploy it to our test server (Windows 2008 R2 SP1) now fails:
Error Code: ERROR_APPPOOL_VERSION_MISMATCH
More Information: The application pool that you are trying to use
has the 'managedRuntimeVersion' property set to 'v4.0'.
This application requires 'v4.5'. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_APPPOOL_VERSION_MISMATCH.
The server has .NET 4.5 installed but there is no app pool 4.5 (because it's inplace upgrade and as I understand 4.0 pool should be fine). The client machine has VS 2012 and so Web Deploy 3 (was Web Deploy 2 previously). I also installed Web Deploy 3 to the server.
Tried to re-register ASP.NET with aspnet_regiis - no luck.
Why do I get the error and how can I fix it? This is so frustrating...
p.s.
Found similar question about RC but it does not help
Update:
Looks like this is a bug Microsoft hasn't fixed since CTP. IgnoreDeployManagedRuntimeVersion property did the trick. What a shame!
You can try adding this property to the project:
<IgnoreDeployManagedRuntimeVersion>True</IgnoreDeployManagedRuntimeVersion>
Windows Server 2012 includes .NET 4.5 by default and (when Web server role added) IIS has the following app pools: DefaultAppPool, .NET v4.5, .NET v4.5 Classic that use .NET Framework 4.0 (because 4.5 is inplace upgrade of 4.0). However, if we install .NET 4.5 redistributable on Windows Server 2008 that has .NET 4.0 installed the pools are not renamed: ASP.NET v4.0, ASP.NET v4.0 Classic. And this is the key why Web Deploy fails.
#kzu: not trying, this will work.
Had the same problem when installing Orchard CMS. Keep targeting v2.0.
But find the simple solution: in IIS, on the Application Pools (the list with all application pools), you can find the 2nd setting top right list: "Set Application Pool Defaults.." change there the default from 2.0 to 4.0 et, voila.
Register ASP.NET for IIS
a. Run CMD as Admin
b. CD to \windows\microsoft.net\framework\v4.x
c. Aspnet regiis -i

Deploying mvc project to iis 6.0

I am trying to deploy my mvc project on windows server 2003 IIS6.
I have enabled the wildcard mapping
.net framework 3.5 sp1 and mvc 1.0 is installed on the machine
I am still getting 404 when I try to access the site
What other steps should I debug to solve this problem?
Ps: Other non-mvc .net project is running fine on the machine
my problem was not referencing the 64bit version of aspnet_isapi.dll - i am running on win2003 64bit

Resources