aspdotnet-suresh offers articles and tutorials,csharp dot net, articles and tutorials,VB.NET Articles,Gridview articles,code examples of 2.0 /3.5,AJAX,SQL Server Articles,examples of .net technologies

what are the Difference between ASP.NET 2.0 and ASP.NET 3.5 | Multi Targeting in | what are the 3.5 features

Oct 7, 2011
Here I will explain about differences between 2.0/3.0/3.5. Generally we will see the questions like difference between 2.0, 3.0 and 3.5 but there is no 3.0 version. We have a version of 3.0 .NET Framework.

Check below table for the differences between 2.0 and 3.5

Feature 2.0 3.5
New Features 2.0 includes the following new features
1)    Master Pages
2)    Profiles
3)    Girdivew Control 3.5 includes the following new features
1)    Listview Control
2)    DataPager Control
3)    Nested Master Pages
4)    Linq DataSource
Multi Targeting 2.0 does not support multi-targeting environment 3.5 supports multi –targeting What is multi – targeting? Check below description
Ajax Support
There is no built-in support for AJAX in 2.0 , it has to be installed and downloaded
In 3.5, Ajax is integrated in .NET framework, thereby making the process of building intuitive cool user interfaces easier
Silverlight Support
It does not support for silverlight
It support for silverlight
JavaScript Debugging
It does not support for JavaScript debugging
It support for JavaScript debugging
LINQ Support
It doesn’t support LINQ
It supports LINQ

What is Multi-Targeting?

With the past few releases of Visual Studio, each Visual Studio release only supported a specific version of the .NET Framework.  For example, VS 2002 only worked with .NET 1.0, VS 2003 only worked with .NET 1.1, and VS 2005 only worked with .NET 2.0.

One of the big changes we are making starting with the VS 2008 release is to support what we call "Multi-Targeting" - which means that Visual Studio will now support targeting multiple versions of the .NET Framework, and developers will be able to start taking advantage of the new features Visual Studio provides without having to always upgrade their existing projects and deployed applications to use a new version of the .NET Framework library.

Now when you open an existing project or create a new one with VS 2008, you can pick which version of the .NET Framework to work with - and the IDE will update its compilers and feature-set to match this.  Among other things, this means that features, controls, projects, item-templates, and assembly references that don't work with that version of the framework will be hidden, and when you build your application you'll be able to take the compiled output and copy it onto a machine that only has an older version of the .NET Framework installed, and you'll know that the application will work.

If you enjoyed this post, please support the blog below. It's FREE!

Get the latest,, VB.NET, jQuery, Plugins & Code Snippets for FREE by subscribing to our Facebook, Twitter, RSS feed, or by email.

subscribe by rss Subscribe by RSS subscribe by email Subscribe by Email


Anonymous said...

Artical is good , i am waiting for the next artical on LINQ.

Unknown said...


vasikarla suresh kumar said...


Anonymous said...

good one.thanks

Anonymous said...

Sir .... your blog is super.... the way of teaching is too fantastic... kindly write something about linq....

Unknown said...

Please update to linq......

Anonymous said...

user friendly...

Anonymous said...

Very simply and easily understandable...thanks for the information

Anonymous said...

awesome...iits really helpful

Anonymous said...

Your guidence are such important and helpful to me.i really like effort that you are making behind this on.e

Anonymous said...

hello sir.....since 3 months i am following your is absolutely too good,, there is no issue.....
i want to learn trying to get it from your site...but am not founding
so please post a linq concept & sample

Anonymous said...

Nice Article...

Give your Valuable Comments

Note: Only a member of this blog may post a comment.

© 2015 All Rights Reserved.
The content is copyrighted to Suresh Dasari and may not be reproduced on other websites without permission from the owner.