Applicability of vs-threading lib and analyzers in ASP.NET

[abergs]

I'm simply wondering if there are any issues with using this nuget and analyzer in an asp.net project?

1: Will it introduce anything bad?
2: Are there any analyzers (AsyncLazy?) that does not apply to a asp.net project and should be ignored?

I asked this question on SO for increased visibility/SEO when others encounter this: https://stackoverflow.com/questions/55103194/using-vs-threading-in-asp-net-project

[AArnott]

VSTHRD200 may not be a good fit if your controller methods are async but you don't want Async as a suffix to those methods because that would influence the public URLs.
VSTHRD012 may not apply either, since you probably don't have a JoinableTaskFactory in an ASP.NET environment.

A couple of others may not apply (VSTHRD001 and VSTHRD003), but they won't likely produce diagnostics in that context either so not so much of an issue.

[Eli-Black-Work]

@AArnott Would VSTHRD011 also not be applicable to ASP.NET Core apps?

[AArnott]

VSTHRD011 is probably not necessary in that case, since it's primarily around avoiding deadlocks in an environment with a main thread.

[Eli-Black-Work]

@AArnott Thanks! 🙂

Do you think it'd be worth noting in the documentation which analyzers aren't applicable to apps that don't have a main thread? (Or maybe more broadly, apps that don't have a threading context, although I'm not sure if that's correct?)

[AArnott]

I think that's a good idea. In fact, we could perhaps document it in terms of .editorconfig files that have the rule severity configured for each app type, so folks could just copy and paste the rule severities into their own files. Care to open a new issue to track that (docs and/or .editorconfig files)?

[Eli-Black-Work]

Filed at #1095 🙂