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.

what is the three pillar of .Net ?

11 Answers  

---

Explain .net Framework?

1 Answers  

---

Is dapper faster than entity framework?

0 Answers  

---

Can you set the unlimited length for "maxjsonlength" property in config?

0 Answers  

---

Explain entity lifecycle? : Entity framework

0 Answers  

---

What is "out" parameter how it is used in methods?

6 Answers   Polaris,

---

mention what are the various methods provided by the dataset object to generate xml?

0 Answers   Microsoft,

---

How would you deploy your old applications with .net framework 4.0? Are the old applications compatible?

0 Answers  

---

Explain the advantage of packaging over xcopy in .net?

0 Answers  

---

Can you write a class without specifying namespace? Which namespace does it belong to by default?

1 Answers  

---

How Garbage Collector identifies the objects which are not in use?

6 Answers   EXL, Honeywell, Microsoft, Tech Mahindra, Tesco,

---

What are the features that are new in .net 2.0

2 Answers   Emphasis,

---