Answer / swapna

Each assembly has a version number called the compatibility
version. Also each reference to an assembly (from another
assembly) includes both the name and version of the
referenced assembly.The version number has four numeric
parts (e.g. 5.5.2.33).

Assemblies with either of the first two parts different are
normally viewed as incompatible. If the first two parts are
the same, but the third is different, the assemblies are
deemed as 'maybe compatible'.

If only the fourth part is different, the assemblies are
deemed compatible. However, this is just the default
guideline - it is the version policy that decides to what
extent these rules are enforced. The version policy can be
specified via the application configuration file.

When was .NET announced

1 Answers  

---

what is ADO.NET

8 Answers   NIIT,

---

How does �side by side� work for the .net framework 3.0?

0 Answers  

---

When using razor views, do you have to take any special steps to protect your asp.net mvc application from cross site scripting (xss) attacks?

0 Answers  

---

What is iobjectset? : Entity framework

0 Answers  

---

Is any files are generated,when we are adding the web reference to the web service?

2 Answers  

---

Does Tempdata hold the data for other request in ASP.Net MVC?

0 Answers  

---

What are Resource Files ? How are they used in .NET

1 Answers  

---

what is entity framework advantage?

0 Answers   Microsoft,

---

What is the use of JIT

1 Answers  

---

More on CLR ?

2 Answers   MMTS,

---

Why doesn't the .NET runtime offer deterministic destruction

1 Answers  

---