{"id":1148,"date":"2016-03-08T01:14:57","date_gmt":"2016-03-08T01:14:57","guid":{"rendered":"http:\/\/blog.wholetomato.com\/?p=1148"},"modified":"2019-05-03T17:28:03","modified_gmt":"2019-05-03T21:28:03","slug":"compatibility-of-visual-assist-with-releases-of-an-ide","status":"publish","type":"post","link":"https:\/\/stage.wholetomato.com\/blog\/compatibility-of-visual-assist-with-releases-of-an-ide\/","title":{"rendered":"Compatibility of Visual Assist with Releases of an IDE"},"content":{"rendered":"

A few days ago, Microsoft announced<\/a> the release candidate (RC) of Visual Studio 2015 Update 2. If you are a user of Visual Assist in this newest Microsoft IDE, any build of Visual Assist beginning with 2073 should work for you. I write “should” because builds of Visual Assist made before the RC, for obvious reasons, have not been tested against the RC. (We can’t test what we don’t have.)<\/p>\n

Builds of Visual Assist usually install to a particular IDE if you have any flavor of it: beta, RC, or RTM. Only when we announce full support for a flavor are you assured we have successfully run our full suite of tests against it. And, only then should you expect complete compatibility between Visual Assist and your IDE.<\/p>\n

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

As for timing, we don’t synchronize our builds and those of Microsoft. But because we issue six or seven builds of Visual Assist a year, one is destined to ship not long after every Microsoft release. That said, the next build we ship may or may not fully support the Microsoft release. Before tackling\u00c2\u00a0full support, we\u00c2\u00a0consider the readiness of our next build at the time of Microsoft announcement, the scope of delay to provide\u00c2\u00a0full support, the assumed quality of Microsoft’s release, and the estimated shelf-life of that\u00c2\u00a0release.<\/p>\n

We give top priority to Microsoft RTM releases; the build of Visual Assist that follows an RTM almost always fully supports it. Other Microsoft releases are usually rolled into our normal development cycle, and they are also the releases that require\u00c2\u00a0the most development time.<\/p>\n

We are already aware\u00c2\u00a0of two conflicts between\u00c2\u00a0the release candidate of Visual Studio 2015 Update 2 and Visual Assist build 2089<\/a>, our latest. We expect to address these in our next build:<\/p>\n

    \n
  1. line breaks are doubled during in-line expansion of VA Snippets. The behavior\u00c2\u00a0is likely due to a bug in Update 2. For now, don’t use your\u00c2\u00a0affected VA Snippets or edit\u00c2\u00a0expanded code.<\/li>\n
  2. a new feature for C# users in Update 2 inserts * at the start of new lines when writing \/**\/ comments. That feature conflicts with the more powerful “Auto-extend Multi-line Comments<\/a>” feature in Visual Assist. For now, disable one or the other.<\/li>\n<\/ol>\n

    If you subscribe to any of our social channels, you will learn about our builds and the IDE flavors they support. If you are ahead of us, meaning you use Visual Assist in a flavor of an IDE that Visual Assist\u00c2\u00a0does not yet fully support, we ask that you report incompatibilities<\/a> between Visual Assist and your IDE. Your reports\u00c2\u00a0help us\u00c2\u00a0attain full support.<\/p>\n","protected":false},"excerpt":{"rendered":"

    A few days ago, Microsoft announced the release candidate (RC) of Visual Studio 2015 Update 2. If you are a user of Visual Assist in this newest Microsoft IDE, any build of Visual Assist beginning…<\/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":[103],"tags":[],"class_list":["post-1148","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfhqii-iw","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1148","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=1148"}],"version-history":[{"count":8,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1148\/revisions"}],"predecessor-version":[{"id":1157,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/posts\/1148\/revisions\/1157"}],"wp:attachment":[{"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/media?parent=1148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/categories?post=1148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.wholetomato.com\/blog\/wp-json\/wp\/v2\/tags?post=1148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}