My prediction is that community involvement in .NET will die on the vine. If .NET is just another community-maintained project, then why use it (and/or contribute to it) over more popular (and therefore more feature-rich and bug-free) languages, such as Python? (Maybe the speed of the .NET runtime over the Python runtime, but most people don't need it).
IMHO the major value proposition in .NET is that it has that top-down leadership from Microsoft, where you don't have to think about what library to use, because it's already baked into the standard library. It may not be perfect, but it's workable. (For instance, people get very opinionated about HTML formatting libraries, and .NET previously - last time that I checked, anyway - had one or two built-in, usually one that was "blessed" and one that was "legacy". Now presumably there are dozens of community-supported libraries, making it a similar situation to the Node/JS ecosystem. Which do you pick?)
IMHO the major value proposition in .NET is that it has that top-down leadership from Microsoft, where you don't have to think about what library to use, because it's already baked into the standard library. It may not be perfect, but it's workable. (For instance, people get very opinionated about HTML formatting libraries, and .NET previously - last time that I checked, anyway - had one or two built-in, usually one that was "blessed" and one that was "legacy". Now presumably there are dozens of community-supported libraries, making it a similar situation to the Node/JS ecosystem. Which do you pick?)