In Visual Studio “14” CTP (in response to a UserVoice request<\/a>) these files can also be added to a Visual C++ project for easier management and source control integration. All you have to do is add the .natvis<\/tt> file to your .vcxproj<\/tt> file.<\/p>\n Here is an example. Suppose we have the following code:<\/p>\n If you run this in debugger you can inspect the value of p<\/tt> and it looks like this: To change the way the point<\/tt> objects are visualized create a file called point.natvis<\/i> with the following content:<\/p>\n Add this file to the project. UPDATE<\/strong> For more see Project Support for Natvis<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Visual Studio 2012 introduced a new framework for writing debugger visualizers for C++ types that replaced the old autoexp.dat file. The new framework offers xml syntax, better diagnostics, versioning and multiple file support. Visualizers are defined in XML files with extension .natvis. These visualizers are loaded each time the debugger starts. That means if you … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[7,52,10],"tags":[35,299,414,458,55,413],"class_list":["post-1842","post","type-post","status-publish","format-standard","hentry","category-c","category-tools","category-visual-studio","tag-debugger","tag-native","tag-natvis","tag-tools","tag-visualstudio","tag-vs14"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\r\nstruct point\r\n{\r\n double x;\r\n double y;\r\n double z;\r\n};\r\n\r\nint main()\r\n{\r\n point p { 1.0, 2.0, 3.0 };\r\n\r\n\treturn 0;\r\n}<\/pre>\n
\n![\"natvis1\"](\"http:\/\/mariusbancila.ro\/blog\/wp-content\/uploads\/2014\/06\/natvis1.png\")
<\/a><\/p>\n\r\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n<AutoVisualizer xmlns=\"http:\/\/schemas.microsoft.com\/vstudio\/debugger\/natvis\/2010\">\r\n \r\n <Type Name=\"point\">\r\n <DisplayString>{{point X={x}, Y={y}, Z={z}}}<\/DisplayString>\r\n <Expand>\r\n <Item Name=\"axis-X\">x<\/Item>\r\n <Item Name=\"axis-Y\">y<\/Item>\r\n <Item Name=\"axis-Z\">z<\/Item>\r\n <\/Expand> \r\n <\/Type>\r\n \r\n<\/AutoVisualizer>\r\n<\/pre>\n
\n![\"natvis3\"](\"http:\/\/mariusbancila.ro\/blog\/wp-content\/uploads\/2014\/06\/natvis3.png\")
<\/a>
\nWhen you run the application in debugger again the point<\/tt> object is visualized according to the per-project .natvis<\/tt> file.
\n![\"natvis2\"](\"http:\/\/mariusbancila.ro\/blog\/wp-content\/uploads\/2014\/06\/natvis2.png\")
<\/a><\/p>\n
\nThere are two things to note:<\/p>\n\n