Answer / gautam

debug mode built always comes up with debug info and it's
for diagnostic purpose only. so size will be bigger and you
can debug it with the help of visual studio and with some
diagnostic apis/macros.

once you are sure there is nothing to debug, need to make a
final built (release mode). it will remove debug info,
strip off debug/diagnostic specific calls from your code.
so, size will be small, optimized, faster(hopefully) and
ready to ship.

Answer / sachin mahajan

Size of exe is more in Debug than in release and hence
release is faster.
Debug contains debugging symbols information and
Release does not have.

Answer / prakash

In release mode all data are clear and you can save it,but
in debugging mode lock all data when not change or correct
data insert in that line or data.

Answer / aditya

i think there us more to release & debug modes than just
size of .exe files & data locking....for eg while making a
dll only a release mode can be used....can anyone be a
little bit more clear....please.

Have you ever used win32 APIs ?

4 Answers   Microsoft,

---

What is socket?

3 Answers  

---

What does mfc stand for?

0 Answers  

---

what is message loop how mfc does it internally?

4 Answers   Aspire,

---

how many types of messages are their

4 Answers   E Logic, TCS,

---

Psychic Window Technique

2 Answers   E Logic, Wild Net,

---

What is subclassing?

2 Answers  

---

What is the use of OninitDialog ?

11 Answers   HCL, Nagarro,

---

Types of DLL's

11 Answers   Invensys,

---

Differ GetMessage, PostMessage & PeakMessage?

4 Answers   Symphony,

---

What is the difference between GetMessage and PeekMessage ?

3 Answers  

---

How can update edit control data of an executing application from other application?

3 Answers   HP,

---