Answer / kirti

There is a once-per-process-per-type overhead with XmlSerializer. So the first time you serialize or deserialize an object of a given type in an application, there is a significant delay. This normally doesn't matter, but it may mean, for example, that XmlSerializer is a poor choice for loading configuration settings during startup of a GUI application.

Explain entity lifecycle? : Entity framework

0 Answers  

---

What is the domain object?

0 Answers  

---

Which .net framework is installed?

0 Answers  

---

How can you return string result from Action in ASP.Net MVC?

0 Answers  

---

What is the necessity for singning an assembly with a strong name?

1 Answers   L&T,

---

---

How do you register the dotnet component or assembly ?

1 Answers   Accenture, BirlaSoft,

---

What is code first? : Entity framework

0 Answers  

---

How do you initiate a string without escaping each backslash ?

1 Answers  

---

What is the advantage of mvc?

0 Answers  

---

Can u tell me differences which are introduced in .Net 1.1 and 2.0 and 3.0 and also in 3.5 ? by detailed?

1 Answers   ABC,

---

How could we achieve Langauge Interoperability through "CLS"?? Please Expalin in detail with Example.. Thanks for the Help!!!!!

2 Answers   HCL,

---

When do you absolutely have to declare a class as abstract

1 Answers   Siebel Systems,

---