Hotreload not working in .cshtml files while debugging UNLESS the project configuration is literally named "Debug"

[alex-jitbit]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I've spent MONTHS investigating this. Finally found the cause.

My project's debug configuration is named FullDebug not the default Debug. But all the settings replicate a debugging config. Code optimizations are disabled, pdb-generation is enabled, I can successfully step through the code in VS2022, examine snapshots, call stacks etc. etc.

<Configurations>Full;Trial;FullCompany;FullSmall;FullDebug</Configurations>
<!--skipped some code-->
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='FullDebug|AnyCPU'">
	<DefineConstants>DEBUG;TRACE;FULL</DefineConstants>
</PropertyGroup>

But hot reload in Visual Studio is not working while debugging (F5), UNLESS MY CONFIGURATION IS LITERALLY NAMED "Debug". Even though my FullDebug configuration mirrors Debug settings

As soon as I rename my configuration to "Debug" hot reload starts working again. What a nonsense.

Expected Behavior

Should work

.NET Version

6.0

Anything else?

Please don't use magic strings.

[javiercn]

@alex-jitbit thanks for contacting us.

You might get a better and faster answer if you report this issue through the Report a problem with Visual Studio - Visual Studio (Windows) | Microsoft Docs UI

[tmat]

@alex-jitbit Could you double-check that the following properties are set like so in your custom configuration?

    <Optimize>false</Optimize>
    <DebugSymbols>true</DebugSymbols>

[alex-jitbit]

@tmat yes they are, and like I said renaming the config helps

[tmat]

Can you share the project privately? What kind of project is it?

[tmat]

Never mind, I have a repro with Web App:
Repro.zip

[MaxenceMouchard]

Hello !
I opened a ticket on visual studio about this because I have the same problem.
This should be fixed in a future release according to the support team
Ticket here

[MaxenceMouchard]

Has been fixed today, this ticket should be able to be closed

[BluMichele]

The issue persists in Visual Studio 2022 17.8

[mkArtakMSFT]

@BluMichele can you provide a repro please, because we thought this was fixed (at least the original report).