4.6.1 framework update leaves web.config httpRuntime still at 4.5?

web-config .net-4.5 httpruntime .net-4.6.1
Kakoritz picture Kakoritz · Apr 7, 2016 · Viewed 10.7k times · Source

i recently upgraded our c# Web Applications to use .net framework 4.6.1 from 4.5 and only today noticed in the web.configs the .net version differs from the .net version. Everything seems to work fine in production but my questions is, since the httpRuntime did not auto change to 4.6.1, i'm curious if thats intentional or do i need to manually key that in or is there some other reason for it to be on 4.5?

Answer

mattfei picture mattfei · Apr 30, 2016

The main purpose of runtime target framework is for compatibility. Some breaking change may be introduced in the new version of asp.net. In order not to break the existing application, the breaking change is quirked through the target framework. You can find more details through this blog.

Related questions

Web.config with XDT transform to do partial replace

I am in a situation where I just want to update a part of a the URL of a WCF endpoint. Right now we do this by including different configs with all the endpoints per 'variety'. This is tedious to …

Read More
Setting up connection string in ASP.NET to SQL SERVER

I'm trying to set up a connecting string in my web.config file (Visual Studio 2008/ASP.NET 3.5) to a local server (SQL server 2008). In my web.config, how and where do I place the connection string? Here's what web.config …

Read More
Login failed for user 'IIS APPPOOL\ASP.NET v4.0'

I have a web project (C# Asp.Net, EF 4, MS SQL 2008 and IIS 7) and I need to migrate it to IIS 7 locally (at the moment works fine with CASSINI). Locally in IIS I have my Default Web Site with my …

Read More