Answer Posted / robert

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 Framework provides operating systems with a Global
Assembly Cache. This Cache is a repository for all the .Net
components that are shared globally on a particular
machine. When a .Net component is installed onto the
machine, the Global Assembly Cache looks at its version,
its public key, and its language information and creates a
strong name for the component. The component is then
registered in the repository and indexed by its strong
name, so there is no confusion between different versions
of the same component, or DLL.

What is a Cookie? Where is it used in ASP.NET?

1146

---

Explain the disadvantages of viewstate?

1161

---

What is state management react?

1090

---

Which methods validate all the controls on a page?

1030

---

Explain significance of routing? : asp.net mvc

1213

---

Explain the difference between server.transfer and response.redirect? Why would I choose one over the other?

1068

---

How many web config files can be created for an application?

909

---

What are the disadvantages of using session?

1178

---

What is the difference between typeof() vs gettype()?

1171

---

What do you mean by serialize?

1037

---

How you can add an event handler?

1017

---

What is autopostback in dropdownlist in asp net?

1043

---

Why do we use sessions?

1060

---

What is role-based security in asp.net?

1147

---

When cookie will expire?

1052

---