{"id":1518,"date":"2019-01-24T15:22:18","date_gmt":"2019-01-24T19:22:18","guid":{"rendered":"http:\/\/blog.wholetomato.com\/?p=1518"},"modified":"2019-05-03T17:27:33","modified_gmt":"2019-05-03T21:27:33","slug":"visual-assist-build-2302-is-available","status":"publish","type":"post","link":"https:\/\/stage.wholetomato.com\/blog\/visual-assist-build-2302-is-available\/","title":{"rendered":"Visual Assist build 2302 is available"},"content":{"rendered":"

Honestly, the title of this post should be “Visual Assist build 2302 has been available for a long time”. I have been lax in writing.<\/p>\n

Fortunately, if you enable notifications of new builds in the options dialog of Visual Assist, you would have discovered build 2302 not long after it was released. And if you clicked through a what’s-new link, you would have learned what improved with the build. I write today primarily for those who\u00c2\u00a0do not get in-product notifications of new builds yet follow these build announcements.<\/p>\n

Build 2302, released mid-December, is a follow-on to build 2301\u00e2\u20ac\u201da build that did not reach the threshold of in-product notifications. Hence, this post describes what’s new in builds 2302 and 2301.<\/p>\n

\"\"<\/p>\n

If you are one to “access the future of Visual Studio” and are already experimenting with Visual Studio 2019<\/a>, build 2302 has preliminary support for the preview build of the IDE.\u00c2\u00a0See our\u00c2\u00a0release notes<\/a>\u00c2\u00a0for known issues.<\/p>\n

For those of you who have debugged multi-threaded applications, you have undoubtedly been annoyed by the debugger’s switching to a thread you are *not* debugging only because another thread hit a breakpoint. You lose context and have no easy way to return to debugging of the first thread.<\/p>\n

Build 2301 introduces a command, Bind Breakpoints to the Current Thread, that does what its name implies. When enabled, other threads that hit breakpoints are automatically continued, and you can debug in peace. Toggle the command via icon in the Visual Assist toolbar, or entry in the VAssistX menu (Alt+X, B, T).<\/p>\n

\"\"<\/p>\n

Build 2301 introduces another command,\u00c2\u00a0Skip All Breakpoints, to improve the debugging experience in Visual Studio. Until the build, switching between the debugging of different parts of an application was cumbersome. One could not tell the debugger to honor only breakpoints in a single part of an application; one had to skip unrelated breakpoints individually, or disable and lose them all. With Skip All Breakpoints, you can effectively toggle all unrelated breakpoints so they are skipped automatically. To debug one part of an application, Skip All Breakpoints, then return breakpoints in the one part to their default state. Get to the command via icon in the Visual Assist toolbar, or entry in the VAssistX menu (Alt+X, B, B).<\/p>\n

\"\"<\/a><\/p>\n

For those who use Source Links to\u00c2\u00a0connect substrings in comment blocks to external applications and websites, you will be pleased to know that Visual Assist [finally] supports sharing of link definitions. When a solution is open,\u00c2\u00a0create a shared solution definition via the Add-button drop-down.<\/p>\n

\"\"<\/a><\/p>\n

Shared solution definitions are created in a subdirectory of the solution directory, .va\\shared\\SourceLinks,\u00c2\u00a0that can be checked into source control that, in turn, makes the shared definition available in read-only mode to all users of Visual Assist.<\/p>\n

Builds 2302 and 2301 also improve\u00c2\u00a0support for Unicode and UTF-8, and improve code generation for users of Unreal Engine 4 (UE4).<\/p>\n

Build 2302\u00c2\u00a0requires software maintenance through 2018.12.13.<\/p>\n

Check out the complete list of what\u00e2\u20ac\u2122s new in build 2302<\/a>; learn more about the\u00c2\u00a0debugging features in Visual Assist<\/a>, or download the installer for build 2302<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Honestly, the title of this post should be “Visual Assist build 2302 has been available for a long time”. I have been lax in writing. Fortunately, if you enable notifications of new builds in the…<\/p>\n","protected":false},"author":28485711,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"footnotes":""},"categories":[10673833],"tags":[],"class_list":["post-1518","post","type-post","status-publish","format-standard","hentry","category-build-announcements"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfhqii-ou","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/users\/28485711"}],"replies":[{"embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/comments?post=1518"}],"version-history":[{"count":16,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions"}],"predecessor-version":[{"id":1541,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions\/1541"}],"wp:attachment":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/media?parent=1518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/categories?post=1518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/tags?post=1518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}