{"id":1192,"date":"2016-05-12T19:34:02","date_gmt":"2016-05-12T23:34:02","guid":{"rendered":"http:\/\/blog.wholetomato.com\/?p=1192"},"modified":"2019-05-03T17:28:03","modified_gmt":"2019-05-03T21:28:03","slug":"visual-assist-build-2097-is-available","status":"publish","type":"post","link":"https:\/\/stage.wholetomato.com\/blog\/visual-assist-build-2097-is-available\/","title":{"rendered":"Visual Assist build 2097 is available"},"content":{"rendered":"

Visual Assist build 2097 introduces support for Visual Studio Enterprise \u201c15\u201d Preview 1, just in time for Microsoft\u2019s posting of Preview 2.<\/p>\n

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

If you use Preview 1, you can install build 2097 assuming\u00c2\u00a0you installed the IDE using its ISO or web installer. The Visual Assist installer for build 2097 won\u2019t recognize your IDE if you installed it only\u00c2\u00a0using Microsoft\u2019s new, \u201clight\u201d installer.<\/p>\n

If you already switched to Preview 2, you should wait for the next build of Visual Assist, due in a few days. That build will officially support Preview 2. (We\u2019ll drop support for Preview 1 at the same time.)<\/p>\n

Also in build 2097, we implemented a suggestion that came to us from a customer at last month\u2019s Build conference\u00e2\u20ac\u201dto support an alternate location for roaming data. The customer envisioned\u00c2\u00a0a more efficient way to configure Visual Assist in multiple VMs and PCs. He wants to store data on OneDrive such that a VA Snippet created in one development environment will\u00c2\u00a0be available when starting an IDE in his other environments. Build 2097 makes that possible, and OneDrive should work just fine.<\/p>\n

With build 2097, one can specify an alternate location for per-user data, e.g. VA Snippets. But, keep in mind Visual Assist won\u2019t automatically write\u00c2\u00a0its registry settings in the alternate location; you need to force that with\u00c2\u00a0export\/import\u00c2\u00a0when you\u00c2\u00a0setup\u00c2\u00a0a new environment.\u00c2\u00a0Export is available on the Performance page of the options dialog for Visual Assist, and \u201cimport\u201d implies running the\u00c2\u00a0exported\u00c2\u00a0registry script in your new environment. (Edit your registry script if file paths of your\u00c2\u00a0two environments\u00c2\u00a0differ, and export\/import works only to\u00c2\u00a0the same version of IDE.)<\/p>\n

Also at the Build conference, we learned very few of our customers are aware of, much less use, VA Hashtags. We demo\u2019d the feature regularly, and every viewer was duly impressed. They had no idea such a simple yet powerful feature of Visual Assist escaped them.<\/p>\n

I mention VA Hashtags for two reasons: if you don\u2019t know about them, you are in for a treat. If you do use them, build 2097 makes it a little easier to hide specific VA Hashtags from all of your solutions, usually the VA Hashtags created solely by and for another developer on your team.<\/p>\n

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

Build 2097 also contains the typical slew of bug fixes.<\/p>\n

Learn how to specify an alternate location for per-user data<\/a>, introduce yourself to VA Hashtags<\/a>, make global hiding<\/a> a little easier, check out the complete list of what\u2019s new in build 2097<\/a>, or download the installer<\/a>.<\/p>\n

One final note, build 2097 doesn\u2019t appear on our downloads page because the build throws an exception for first-time users of Visual Assist. If\u00c2\u00a0you are reading this blog post, it\u2019s a safe bet you are not a first-time user; you won\u2019t see the exception. Our next build will fix\u00c2\u00a0the problem\u00c2\u00a0and will appear on our downloads page for all users.<\/p>\n","protected":false},"excerpt":{"rendered":"

Visual Assist build 2097 introduces support for Visual Studio Enterprise \u201c15\u201d Preview 1, just in time for Microsoft\u2019s posting of Preview 2. If you use Preview 1, you can install build 2097 assuming\u00c2\u00a0you installed 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-1192","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-je","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1192","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=1192"}],"version-history":[{"count":16,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1192\/revisions"}],"predecessor-version":[{"id":1210,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1192\/revisions\/1210"}],"wp:attachment":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/media?parent=1192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/categories?post=1192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/tags?post=1192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}