Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Using the C# Debugger shows different Views than when using dotnet run

Abierto
  • ¿Algo no está bien?
#9,554 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
csharp, vscode
Área
devtools

Línea de trabajo

Comienza comparando la configuración predeterminada del depurador en .vscode/launch.json con la ruta de terminal dotnet run; después, inspecciona cómo el depurador gestiona program.cs, Register.cshtml, Register.cshtml.cs y las vistas y archivos .resx relacionados. La tarea estará terminada cuando el depurador y dotnet run carguen las mismas vistas generadas por el scaffolding, campos y valores localizados.

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

Descripción

Debugger untriaged

Environment data

.NET SDK:
Version: 10.0.300
Commit: caa81fa497
Workload version: 10.0.300-manifests.b47d7e23
MSBuild version: 18.6.3+caa81fa49

Runtime Environment:
OS Name: org.freedesktop.platform
OS Version: 25.08
OS Platform: Linux
RID: linux-x64
Base Path: /usr/lib/sdk/dotnet10/lib/sdk/10.0.300/

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
Version: 10.0.8
Architecture: x64
Commit: 94ea82652c

.NET SDKs installed:
10.0.300 [/usr/lib/sdk/dotnet10/lib/sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 10.0.8 [/usr/lib/sdk/dotnet10/lib/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 10.0.8 [/usr/lib/sdk/dotnet10/lib/shared/Microsoft.NETCore.App]

Steps to reproduce

  1. Project Setup
  • Create a new MVC Project with Authentication enabled. Choose Individual Accounts for type.
  • Scaffold the Register.cshtml page for a custom User class that inherits from IdentityUser by using the steps described in the official documentation for scaffolding Account pages.
  • Make sure this User class has additional fields like First Name and Last Name
  • Open the Register.cshtml page and add the additional fields for First Name and Last Name
  • Open Register.cshtml.cs and expand Input to include the new fields.
  • Set the First Name and Last Name fields in the custom User class in OnPostAsync in Register.cshtml.cs
  1. Debugger Setup
  • Create the launch.json file in .vscode
  • Use the default .NET Core Launch (Web) setup
  • Change the "program" path to the .dll file.

Debugging

  • Debug the program, the View Index cannot be found.
  • Stop the Debugger and update program.cs by adding RazorRuntimeCompilation to the Services (needs NuGet Package)
  • Debug the Program again. Views work now. Navigate to the Register page.
  • The View is still the standard Register View and not the scaffolded version with the additional fields.
  • Stop the debugger and open the terminal. Type dotnet run and press enter
  • Navigate to the Register page and notice it now displays the correct View with the fields for First Name and Last Name.

Expected behavior

  • Using both dotnet run and the Debugger should show the same results in Views

Actual behavior

  • Running the app with the Debugger shows different Views. The first image is using the Debugger. The second is when using dotnet run
Image Image

Additional context

  • Similar issues occur when trying to use .resx files for translations. Using a ViewLocalizer in a Razor page will only display the Values when using dotnet run. With the debugger, it simply displays the Keys as the .resx files appear to not be loaded / compiled when using the debugger.
  • This version of VS Code runs in a container, but it has full access to all files outside the container and the problem persists.
Lenguaje dominante
TypeScript
Estrellas
3.1k
Forks
741
Merge medio
1 d 8 h
PR fusionados (30 d)
59

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/vscode-csharp

Todos los issues de dotnet/vscode-csharp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.