Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2018.3.X, 2019.1.X, 2019.3.X



Found in








Issue ID




Unable to find a corresponding location while using Partial classes/methods when debugging



Reproduction steps:

1. Open "Test" project and "SampleScene" scene
2. Open "TestClass.Partial" in VS
3. In Line 9 add a Breakpoint
4. Attach to Unity
5. Enter Playmode
6. Hover over the Breakpoint
7. Notice an error "The breakpoint will not currently be hit. Unable to find a corresponding location"

Expected Result: Debugging works as expected with Partial classes/methods
Actual Result: While debugging, unable to find a corresponding location while using Partial classes/methods

Reproducible with: 2017.4.11f1, 2017.4.34f1, 2018.4.13f1, 2019.2.0a8, 2019.2.13f1, 2019.3.0b11, 2020.1.0a13
Not reproducible with: 2017.4.10f1, 2018.4.3f1, 2019.2.0b6, 2019.3.0a6,

Comments (13)

  1. FlightFight

    May 08, 2019 13:05

    ShikenNugget's solution worked for me in Visual Studio 2019

    "Go Project Settings -> Player -> Other Settings and set the API Compatibility level to .NET 2.0 (as opposed to .NET 2.0 Subset). Restart Visual Studio, Clean and Rebuild the solution. This got rid of the warnings for me. "

  2. stonstad

    Feb 12, 2019 18:21

    Still in issue in 2018.3.1f1 and it is a regression. Ugh!

  3. DigitalGod

    Jan 30, 2019 01:58

    This has been driving me nuts for months. I do use partial classes in my project, but it also happens in ordinary class files, seemingly at random. A whole file will be like this for days or weeks and then suddenly it works again. There's a thread about it here:

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.