.net - Win32 Console app vs. CLR Console app -
i'm working on c++ project don't intend develop or deploy using .net libraries or tools, means make sense me create using visual studio win32 console application. however, i've heard debugging abilities when using clr application under visual studio more powerful. have few questions:
is true having clr app vs. win32 app adds capabilities development process if don't utilize .net libraries or other resources?
if so, still able develop/compile project clr project take advantage of these though i'd developing pure c++ project using stl, etc. , not taking advantage of .net functionality? or such project require fundamental differences make non-trivial revert back, meaning should stick win32 console app?
bottom line answer, if never intending use clr or .net objects in application, use normal win32 c++ library. doing else cause pain down road.
now, answer original question debugging, yes debugging clr has advantages on debugging normal c++ app. starting visual studio 2005, both c# , vb.net began focus on making variable display in locals / autos /watch window more valuable. done through introduction of .net attributes such debuggerdisplay, debuggertypeproxy , visualizer framework.
if don't use .net types though, none of these benefits.
the c++ expression evaluator not take advantage of of these. has it's own methods of customizing type display. it's not featureful (or potentially dangerous) attribute style because doesn't allow code run in debugee process.
that's not debugging c++ provides poor experience. merely different , there better displays many stl container types.
debugging clr app has disadvantegs. instance, debugging optimized code near impossible @ times because jiter hide local variables, parameters , "this". debugging constructed c++ app can frustrating can grab registers , dissamebly see what's going on. doing same clr app difficult @ best.
Comments
Post a Comment