Your official information source from the .NET Web Development and Tools group at Microsoft.
This post introduces you to a small improvement that has been made in Visual Studio 2010 & .NET 4 to reduce the size of the ASP.NET application level web.config
3.0 and 3.5 web.config
As ASP.NET technology evolved, the application level Web.config had new things added to it. Since the earlier frameworks were using the same set of machine level configuration files, incremental feature that was added subsequent to the 2.0 release resulted in additional config settings included in the file.
.NET 4 web.config
With .NET 4, the web.config is tremendously reduced in size to improve the simplicity of ASP.NET
The config settings have been moved down to the machine config file. This includes registers all of the ASP.NET tag sections, handlers, modules and settings for the following:
You can look at the trimmed down web.config by creating a .Net 4 'ASP.NET Empty Web Application' in Visual Studio 2010.
Following is the web.config file for .NET 4 C# 'ASP.NET Empty Web Application':
The config file above has settings to tell ASP.NET to enable debugging by default for the application and provides the version of .NET framework to use.(Please read the post http://blogs.msdn.com/webdevtools/archive/2009/09/30/visual-studio-2010-property-grid-filtering.aspx to find out why targetFramework version attribute should not be updated manually)
Hope this helps,
Deepak Verma | Visual Web Developer
It will be great if you take the pain of elaborating it more... Thanks
it does not needs any elaborarion on this ....
when u take this for any other project , u may take the reference of codeguru.com foor more info...
this reference is actually been taken from my own experiance..
you may take a book from c# book of RUshell c# model....its clearly mentioned that the correct way to dubugging in web.config file is :
authentication model =true: database =localhost; private security hub= open; >
Try this and tell me if it works for u or not..
happy coding.... ;-)
I don't see targetFramework attribute in the capture.
Thanks Alice for pointing that out. I had accidentaly removed the attribute while taking the screen capture. I have updated it with a new capture. Sorry if it created any confusion.
i already seen this from other developers blog and i am so happy for the new update that microsoft made for VS2010. more power.