Member Avatar for jigneshdesai

Can please any one help in understanding the difference between .NET 1.1,2.0,3.0,3.5 and 4.0 ?

  • 3 Contributors
  • 2 Replies
  • 519 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by khadakbist

Dani AI

Generated

gave a good, compact feature summary; this adds the practical bits many developers need later: how the CLR maps to framework releases, what “layered” vs “side‑by‑side” means for installs, how to retarget an app, and quick troubleshooting steps for deployment problems.

A key point not obvious from feature lists: framework version != CLR version. .NET 2.0, 3.0 and 3.5 all run on the same CLR (the 2.x runtime) and are delivered as layered updates — installing 3.5 gives you the 2.0/3.0 functionality as well. .NET 4.x introduced a new CLR (4.x) and can run side‑by‑side with the 2.x stack, so runtime availability on the server matters when you upgrade or deploy. (learn.microsoft.com)

When retargeting a web project, change the project Target Framework in Visual Studio and check Web.config. ASP.NET recognizes the <compilation targetFramework="X.Y" /> setting for version 4.0 and later; if you set a target that isn’t installed on the host you’ll get a configuration error. Example Web.config fragment:

<system.web>
  <compilation debug="false" targetFramework="4.0" />
</system.web>

Test the site on servers that have the target runtime installed before switching production. (learn.microsoft.com)

If you see assembly-version or binding errors after upgrading, use binding redirects and the Fusion Log Viewer to diagnose and fix them. A typical redirect looks like this:

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="MyLib" publicKeyToken="32ab4ba45e0a69a1" culture="neutral" />
      <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>

Use fuslogvw.exe (run as Administrator) to capture bind failures and confirm what the loader is trying to load. (learn.microsoft.com)

Quick checklist before upgrading: run your full test suite on the target CLR, verify third‑party libs and native interop, update CI/build images, validate Web.config settings, and use fusion logs and binding redirects to resolve assembly issues. This complements ’s feature list with the hands‑on steps most deployments require.

Recommended Answers

All 2 Replies

Member Avatar for questpond

The list of differences are huge. In interviews you normally need to short and sweet. So we will list down top 5 differences from each section.

So lets first start with the difference between 1.0 and 2.0.

Support for 64 bit application.
Generics
SQL cache dependency
Master pages
Membership and roles

Now the next difference .NET 2.0 and 3.0
=========================================

WCF
WPF
WWF
WCS ( card space)

3.0 and 3.5
==========================================
LINQ
Ajax inbuilt
ADO Entity framework
ADO data services
Multi targeting

Finally 3.5 and 4.0
===========================================
MEF
Parallel computing
DLR dynamic
Code contract
language runtime
Lazy initialization

Member Avatar for khadakbist

great answer

commented: Sock-puppet nonsense. -3
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.