Leonid Tsarev

Sample code: ``` [HtmlTargetElement("button")] public class ConditionalDisableTagHelper : TagHelper { [HtmlAttributeName("asp-is-disabled")] public bool IsDisabled { set; get; } public override void Process(TagHelperContext context, TagHelperOutput output) { if (IsDisabled) { var...

Unlikely. I'm not specialist in AzDevOps either

@SergeyTeplyakov what do you plan on ErrorProne.Net? Does ErrorProne.Net implements superset of this analyzer or not? Do you think that both projects will be useful on long run?

Please see #24 #25 & #26 in this order

So, basically it's no reason for me to look into ExceptionAnalyzer instead of ErrorProne.Net? Do you have a Nuget build of ErrorProne?

Do you like me for execute same trick as for ExceptionAnalyzer to setup appveyor build for this? :-)

Just to be clear: if I do this, will you setup & publish public nuget builds? :-)

nugets & shared library problem. StructAnalyzer depends on ErrorProne.Net.Core and it will manifests as package depedency. I can package ErrorProne.Net.Core as separate package, but it could lead to conflicts if...

Another idea: make helpers a bunch of cs files directly included to.other projects.

@SergeyTeplyakov seems that nothing prevents you to start publishing ErrorProne.Net.Exceptions builds. If there is something could be contributed from my side, please say :-)