I have reservations about this - I don't think Rider should be responsible for creating procedures such as this. If there's an existing standard way for adding Analysers, then we should support it, but if there isn't, we shouldn't invent one.

@citizenmatt @kskrygan
I haven't got any response in Unity slack about this.
If we don't want to include it directly to our package, I will publish it as a separate gist useful for anybody interested. Rider/VS/Any_other_editor.

With the new Incremental Compiler, there is some support for analyzers, but it isn't documented (and probably not even working yet). I'm not sure what direction they'll take on this, since they've gone kinda silent on the entire Incremental Compiler thing. You might want to try asking Dom_Laflamme about this.

In any case, I think that, even if there is no standard way of adding Roslyn analyzers right now, extending the project generation to be able to have then included is great and might open this path to many.

Separate cs file vad710/UnityEngineAnalyzer#27 (comment)

New and better aproach vad710/UnityEngineAnalyzer#43
Works for Unity 2019.2+