[Roslyn] Tutorial misses information about netCore3.0 (unsupported!) is required to be installed to use the Roslyn .NET Standard Template and succeed with the tutorial

Abierto
#50,386 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
csharp

Línea de trabajo

Comienza con docs/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix.md y compara sus instrucciones sobre el proyecto y el framework de destino con las plantillas actuales de Roslyn SDK y los componentes de Visual Studio Installer. Documenta los componentes necesarios y añade orientación para la solución de problemas o la migración de los destinos de proyecto netstandard2.0, netcoreapp3.1 y net472. Verifica que el tutorial refleje la experiencia actual con las plantillas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

dotnet-csharp/svc roslyn-sdk/subsvc
Type of issue

Missing information

Description

I attempted to create my first Roslyn Generator/Analyzer Project from scratch in VS2026 v18.0.2 using the linked tutorial guide, but just like the user here:

(which should be fixed from the issue state !!! )

and latest updates and workloads provided from the Visual Studio Installer, I run into the same problems:

  • We can not select to get a "real" .NET Standard Project, only be able to choose between different .NET Framework Versions but we not can "opt-out" of using NET Framework.
  • Analyzer (main project), Analyzer.Codefixes, Analyzer.Package Projects are using the to be expected <TargetFramework>netstandard2.0</TargetFramework> in .csproj that doesn't applies on the two other provided Projects!
  • Analyzer.Test is provided with the expected to be fixed and by that not included <TargetFramework>netcoreapp3.1</TargetFramework>
  • Analyzer.Vsix is provided with the previously required to be selected <TargetFramework>net472</TargetFramework>

There is exactly NO Information about both (Framework / .NET Core) installation Components would be required for this tutorial or using the Roslyn SDK Templates, I would ask you to add those critical information into this Documentation and, if you have some, also to suggest to us, how to workaround this or similar. But saying nothing and just awaiting the user to get a bad User Expirience is the worst approach I can think of 👀
and I am sure, that's not your intention 👍

This is the current User Expirience you are providing to us without any changes:

https://github.com/user-attachments/assets/55ed18de-a600-4d63-82dd-4dfa351d89c2

Since the linked sample is not using these issued TFM's, I think someone is aware of this update requirement in your Team and maybe even if you are not the ones relyable for the Tempaltes provided, you could possibly add a kind of migration/Troubleshooting section for this?
Thanks in advance!

Additional Information & Feedback

I did hear already from the requirement to be using netstandard2.0 even if I am not very happy about it, because we are now for regular apps at .NET 10, that would be okay and expected.
Even Visual Studio Installer itself is stating .NET Core 3.1-Runtime as not longer supported so the priority of anyone who is maybe relyable in shipping VS Templates should maybe re-evaluated 😄 :

Image
Page URL

https://learn.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix.md

Document Version Independent Id

a286e20b-1e43-dc57-e0fb-5a9dee7ec3f6

Platform Id

66b66ae2-c045-6e7a-3fc2-550b1ac424ee

Article author

@BillWagner

Metadata
  • ID: 6e3fc905-7aa1-7f5e-9bfe-fbcef461ad5e
  • PlatformId: 66b66ae2-c045-6e7a-3fc2-550b1ac424ee
  • Service: dotnet-csharp
  • Sub-service: roslyn-sdk

Related Issues

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4.8k
Forks
6.1k
Merge medio
22 h 46 min
PR fusionados (30 d)
296

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnet/docs

Todos los issues de dotnet/docs

Issues similares

Más issues de Compilers

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.