将.NET Core应用重定向到net462后断点无法命中

Hey there, I’ve run into this exact issue before when switching between .NET Core and .NET Framework targets in Visual Studio 2017. Let’s walk through the most common fixes to get your breakpoints working again:

1. Double-Check Your Build Configuration #

First, make sure you’re not accidentally in Release mode—this enables code optimization which will skip breakpoints entirely. Look at the dropdown in the top toolbar of VS2017:

• Select Debug from the "Solution Configurations" menu
• Ensure your platform is set to Any CPU (or the appropriate target for your project)

2. Clean & Rebuild Your Project (And Delete Old Outputs) #

Residual build files from the .NET Core target can cause conflicts with the .NET Framework build. Do this step-by-step:

• Right-click your project in the Solution Explorer → Clean
• Then right-click again → Build
• For extra measure, manually delete the bin and obj folders in your project directory (these hold compiled outputs and intermediate files)
• Rebuild the solution once more

3. Verify Debug Project Settings #

Your project’s debug properties might have gotten messed up during the framework switch:

1. Right-click your project → Properties → Go to the Debug tab
2. Under "Startup Action", confirm it’s set to Start project (not a custom executable or URL)
3. Uncheck Enable native code debugging (this is unnecessary for standard .NET Framework console apps and can interfere with managed code debugging)
4. Ensure the "Working directory" points to your project’s output folder (usually bin\Debug\net462—the default should be correct, but double-check)

4. Ensure Debug Symbols Are Being Generated #

If your project isn’t producing .pdb files (debug symbols), breakpoints can’t be mapped to your code. Open your .csproj file and verify these settings exist for the Debug configuration:

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
  <DebugSymbols>true</DebugSymbols>
  <DebugType>full</DebugType>
</PropertyGroup>

If they’re missing, add them and save the file, then rebuild. You should see a .pdb file in your bin\Debug\net462 folder after building.

5. Reset Visual Studio Debug Settings #

Sometimes VS’s internal configuration gets corrupted. Resetting it can fix odd debugging issues:

• Go to Tools → Import and Export Settings
• Select Reset all settings → Follow the prompts (you can save your current settings if you want, but it’s optional)
• Restart VS and try debugging again

6. Disable VS Extensions (Temporarily) #

Third-party extensions can occasionally interfere with debugging. Try disabling all extensions:

• Go to Tools → Extensions and Updates
• Disable every extension listed → Restart VS
• Test your breakpoints—if they work, re-enable extensions one by one to find the culprit

After trying these steps, your breakpoints should start hitting as expected when targeting .NET Framework 4.6.2.

内容的提问来源于stack exchange，提问作者Gigi