Tag: DotNet
-
Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list
You might see following error when browse your application site targeting ASP.NET 4.0 on IIS 7 or 7.5 server. HTTP Error 500.21 – Internal Server Error Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list Cause & Solution If IIS is enabled after DotNet 4 installation then ASP.NET is not registered with IIS.…
-
Configure PowerShell to use DotNet 4.0
You might get following error when you load a snap-in that is written by DotNet 4.0. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. This is because by default, PowerShell uses DotNet version 2.0 CLR. To use powershell load DotNet 4.0 assemblies, the following settings need…
-
Mixed mode assembly Error After Upgrading to DotNet 4.0
After upgrading existing DotNet 2.0 or 3.5 application to DotNet 4.0, you might see following error message Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. To fix this issue, put a config file next to your exe called <exename>.exe.config with…
-
Enable DotNet 3.5 from command line
To enable DotNet 3.5 from command line, run following from elevated command prompt dism.exe /online /enable-feature /featurename:NetFx3
-
Could not load type System.ServiceModel.Activation.HttpModule
If you install DotNet framework 4.0 on Windows Server 2008 or R2 after enabling IIS, you might see following error when browse your application site made of ASP.NET 4.0 (or run on ASP.NET 4.0 application pool). Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’. Description: An unhandled exception occurred during the execution…