{"id":12424,"date":"2020-01-21T11:27:41","date_gmt":"2020-01-21T19:27:41","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/vsnews\/?p=12424"},"modified":"2020-01-21T11:27:41","modified_gmt":"2020-01-21T19:27:41","slug":"aa71a74","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/vsnews\/akams-aa71a74\/","title":{"rendered":"Simplifying Visual State Manager with TargetName"},"content":{"rendered":"<p>The <a href=\"https:\/\/docs.microsoft.com\/en-us\/xamarin\/xamarin-forms\/user-interface\/visual-state-manager\" target=\"_blank\" rel=\"noopener noreferrer\">Visual State Manager<\/a> (VSM) has been around since Xamarin.Forms 3.0, but we\u2019re not done developing it. One of the things we really wanted to add is the ability to change a property on <em>any<\/em> child element within scope. Up until now, you could only set values of properties of the element you applied the VSM to. Recently a PR was merged that changes that for our new Xamarin.Forms 4.5 pre-release version. This functionality will add a lot of extra flexibility to the VSM. In this post I will tell you all about it and show you how to use it yourself.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Visual State Manager (VSM) has been around since Xamarin.Forms 3.0, but we\u2019re not done developing it. One of the things we really wanted to add is the ability to change a property on any child element within scope. Up until now, you could only set values of properties of the element you applied the [&hellip;]<\/p>\n","protected":false},"author":836,"featured_media":8227,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-12424","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allskus"],"acf":[],"blog_post_summary":"<p>The Visual State Manager (VSM) has been around since Xamarin.Forms 3.0, but we\u2019re not done developing it. One of the things we really wanted to add is the ability to change a property on any child element within scope. Up until now, you could only set values of properties of the element you applied the [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/12424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/users\/836"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/comments?post=12424"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/12424\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media\/8227"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media?parent=12424"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/categories?post=12424"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/tags?post=12424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}