{"id":2021,"date":"2013-07-30T12:41:27","date_gmt":"2013-07-30T12:41:27","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2013\/07\/30\/vs-2012-4-update-4-will-exist\/"},"modified":"2024-04-08T12:32:09","modified_gmt":"2024-04-08T19:32:09","slug":"vs-2012-4-update-4-will-exist","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/vs-2012-4-update-4-will-exist\/","title":{"rendered":"VS 2012.4 (Update 4) will exist!"},"content":{"rendered":"<p>Sometime this spring, though for the life of me I can\u2019t find it, I wrote a blog post where I said I thought Update 3 (VS\/TFS 2012.3) would be the last update in the VS\/TFS 2012 update line.\u00a0 I often say that nothing that is said about the future is more than a guess with varying levels of confidence.\u00a0 So, it turns out that I was wrong.\u00a0 A month or two ago we decided that we were going to need to do a 2012.4 release.<\/p>\n<p>The primary motivation is addressing compatibility and migration\/round-tripping issues between VS 2012 and VS 2013 and the various platform releases to make adoption of VS 2013 as smooth as possible.\u00a0 The planned timing will be around the same time VS 2013 releases (and, of course, I can\u2019t give any more detail at this time other than saying that it will be before the end of the year).\u00a0 Once we decide to ship a release like this, it then becomes a vehicle to deliver anything else that would be valuable\/important to deliver in that timeframe.\u00a0 So, for instance Update 4 will also include a roll up of fixes for all important customer reported by the time it locks down.<\/p>\n<p>Like Update 3, Update 4 will be a very scoped release just focused on these compatibility fixes and key customer impacting bug fixes.\u00a0 We will not be delivering significant new features in Update 4.\u00a0 I qualify it with \u201csignificant\u201d because what is a feature and what is a bug fix is in the eye of the beholder.<\/p>\n<p>Today we released the first Release Candidate for Update 4.\u00a0 Don\u2019t take the \u201cRelease Candidate\u201d designation too seriously.\u00a0 We\u2019re going to have several release candidates and it\u2019s still early in the process.\u00a0 I think the primary reason for calling it a release candidate is that we have validated it for production use and we wanted the name to clearly reflect that.\u00a0 So if you\u2019ve got a specific issue that\u2019s addressed in this release, installing it would make sense.\u00a0 Otherwise, I would just wait a little bit for a later release candidate.\u00a0 I\u2019d say that, at this point, less than half the fixes that will ultimately be in the release are in this release candidate.<\/p>\n<p>Here are some resources for RC1:<\/p>\n<ul>\n<li><a href=\"http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=39704\">VS 2012.4 and related downloads<\/a><\/li>\n<li><a href=\"http:\/\/go.microsoft.com\/fwlink\/?LinkId=314228\">VS 2012 Update 4 RC 1 KB Article<\/a><\/li>\n<\/ul>\n<p>You\u2019ll find the specific list of bug fixes so far in the KB article.\u00a0 You\u2019ll also notice most of them are TFS related at this point <a href=\"https:\/\/devblogs.microsoft.com\/bharry\/wp-content\/uploads\/sites\/8\/2014\/02\/8228.wlEmoticon-smile_58CD4724.png\"><img decoding=\"async\" class=\"alignnone size-full wp-image-15586\" src=\"https:\/\/devblogs.microsoft.com\/bharry\/wp-content\/uploads\/sites\/8\/2014\/02\/8228.wlEmoticon-smile_58CD4724.png\" alt=\"Image 8228 wlEmoticon smile 58CD4724\" width=\"19\" height=\"19\" \/><\/a><\/p>\n<p>So now you are going to ask me whether or not there will be an Update 5.\u00a0 At this point, my answer will be \u201cIf we need one.\u201d\u00a0 But, I don\u2019t expect so at this time.<\/p>\n<p>Enjoy!<\/p>\n<p>Brian<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sometime this spring, though for the life of me I can\u2019t find it, I wrote a blog post where I said I thought Update 3 (VS\/TFS 2012.3) would be the last update in the VS\/TFS 2012 update line.\u00a0 I often say that nothing that is said about the future is more than a guess with [&hellip;]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[4],"class_list":["post-2021","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-visual-studio"],"acf":[],"blog_post_summary":"<p>Sometime this spring, though for the life of me I can\u2019t find it, I wrote a blog post where I said I thought Update 3 (VS\/TFS 2012.3) would be the last update in the VS\/TFS 2012 update line.\u00a0 I often say that nothing that is said about the future is more than a guess with [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/2021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=2021"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/2021\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=2021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=2021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=2021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}