Answer Posted / vimal victor

DLL Hell :- This is a problem in loading a specific dll
(class id, version number, path etc). For example, if I
build test.dll v1.0.0.0 and deploying it in c:\MyProg. My
application App1 and App2 are using the methods in that
dll. And there is a requirement to change something in App1
and I supposed to change test.dll also for the same
requirement. Once I finished with all my changes, I will be
deploying them in the appropriate locations. Now, the older
dll will be overwritten. And my App2 will look for test.dll
of older version and since it is not there it will not
work. This is a scenario for dll hell issue.

.NET and dll hell:- .NET has a provision to specify whether
a 'Specific Version' to be loaded or not. If you check with
any dll's propery window, that has a property called
Specific Version. By default it will be false for the dll's
created by users. It means whether the specific version
alone has to be loaded for that project. If that is false,
then te runtime will load any available higher version of
dll for that project. Thus this issue has been sorted out.

What is tracing? Where is it used?

1163

---

How information about the user's locale can be accessed?

1054

---

What is the difference between a multi-layer and multi-tier applications?

1010

---

Explain cashing in asp.net.

982

---

What does the hotspot class in .net do?

999

---

Name the namespace which is used by ado.net?

952

---

What is cross page posting in asp net?

965

---

Explain the Session state management options available with ASP.NET?

1023

---

What is masterpage?

944

---

What is the use of session?

928

---

What are the different types of validation controls in asp.net?

1053

---

How can we make sure that Web API returns JSON data only?

1014

---

What is event in asp.net?

1009

---

What is a url string?

1014

---

Why will you usually create an aspnet user account in the database for an asp.net web application?

1005

---