{"id":228281,"date":"2020-02-11T10:17:19","date_gmt":"2020-02-11T18:17:19","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=228281"},"modified":"2020-02-11T10:43:55","modified_gmt":"2020-02-11T18:43:55","slug":"making-our-unity-analyzers-open-source","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/making-our-unity-analyzers-open-source\/","title":{"rendered":"Making our Unity Analyzers Open-Source\u00a0"},"content":{"rendered":"

Here at the Visual Studio Tools for Unity team our mission is to improve the productivity of Unity<\/a> developers. In Visual Studio 2019 we\u2019ve introduced our Unity Analyzers, a collection of Unity specific code diagnostics and code fixes. Today we\u2019re excited to make our Unity Analyzers Open-Source<\/a>.<\/p>\n

Unity Analyzers<\/h2>\n

Visual Studio and Visual Studio for Mac rely on Roslyn<\/a>, our compiler infrastructure, to deliver a fantastic C# programming experience. One of my favorite features of Roslyn is the ability to programmatically guide developers when using an API. At the core of this experience, an analyzer detects a code pattern, and can offer to replace it with a more recommended pattern.<\/p>\n

A common example that is specific to the Unity API is how you compare tags on your game objects. You could write<\/p>\n

collision.gameObject.tag == \"enemy\";<\/pre>\n
to compare tags<\/p>\n
<\/p>\n
But Unity offers a CompareTag<\/a> method that is more efficient, so we implemented a CompareTag<\/a> diagnostic that will detect this pattern and offer to use the more optimized method instead. On Windows just press (CTRL+.) or press (Alt-Enter) on Visual Studio for Mac to trigger the Quick Fixes, and you\u2019ll be prompted by a preview of the change:<\/p>\n
<\/p>\n
We currently have a dozen analyzers<\/a> that are shipping in the Tools for Unity, with more being written right now.<\/p>\n
Improving the Default Experience<\/h2>\n
Recently the Roslyn team introduced analyzer suppressors. This feature allows us to programmatically suppress the default set of analyzers that Roslyn ships.<\/p>\n
This is great for Unity developers, because it allows the Tools for Unity team to remove warnings or code fix suggestions that do not apply to Unity development.<\/p>\n
A common example is for fields decorated with Unity\u2019s SerializeField<\/a> attributes to light-up the fields in the Unity Inspector. For instance, without the Unity Analyzers, Visual Studio would offer to make a serialized field readonly<\/em> while we know the Unity engine is setting the value of this field. If you were to accept that code fix, Unity would remove any association you set in the Inspector for this field, which could break things. By writing a suppressor, we can programmatically suppress this behavior while keeping it enabled for standard C# fields.<\/p>\n
Available now<\/h2>\n
Today, the Unity Analyzers are being shipped as part of the Tools for Unity and are enabled on Visual Studio and Visual Studio for Mac. The analyzers are running inside Visual Studio, meaning that if you suppress a warning you might still see it in Unity\u2019s error list. We\u2019re working on improving this for a future release.<\/p>\n
Bring your tips and tricks<\/h2>\n
The Tools for Unity team has a backlog of analyzers, code fixes and suppressors that we\u2019re working on, but we\u2019re always on the lookout for new analyzers that would improve the C# programming experience of Unity developers. The project is easy to get started with. Just head to our README and suggest a new analyzer or even submit a PR to the repository.<\/p>\n
See you on GitHub!<\/p>\n","protected":false},"excerpt":{"rendered":"
Making our Unity Analyzers in visual studio Open-Source\u00a0<\/p>\n","protected":false},"author":641,"featured_media":228283,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1195,472,561,155],"tags":[5,179,5608,182,12,452],"class_list":["post-228281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cross-platform","category-gaming","category-open-source","category-visual-studio","tag-csharp","tag-game-development","tag-roslyn","tag-unity","tag-visual-studio","tag-visual-studio-for-mac"],"acf":[],"blog_post_summary":"
Making our Unity Analyzers in visual studio Open-Source\u00a0<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/228281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/641"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=228281"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/228281\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/228283"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=228281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=228281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=228281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}