Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
xamarin nuget with symbols do not debug work unless source is in same location as original build source path #2460
When I create our own nuget packages I have GeneratePackageOnBuild and include symbols (portable) and include source for the .net stanadr projects creating the nugets.
The symbols and debugging works with "normal" .net apps., however, they are not debuggable in Xamavin project. With that said the symbols will work if I replicate the build path (on the service running the agent pool and MSBuild) to be on the same location on my local machine and add the source.
It does not matter what I enter in VS2017 15.9.2 Options->Debugger->Symbols
Again. we need to have the source code in the same location/path as it is on the build server. (this is difficult as each build has its own id) and it will work.
It just appears that the paths must be equal.
changed the title from
xamarin symbols do not work unless source is in same location as original build source path
xamarin nuget with symbols do not debug work unless source is in same location as original build source path
Nov 27, 2018
Can you give a concrete example? XYZ is at path
I emailed you via the email listed on your Github account if you want to share nugets privately.
Yes it is problaby best you replicate your self. Very easy.
To make sure I follow: You are trying to step into the source code of the compiled NuGet?
This sounds like an IDE problem, and not really anything to do with Xamarin.Android.
A couple of things to try:
Hope that helps! Closing for now, as I think you would hit the same problem with a regular .NET console app. Feel free to comment if you find otherwise!
I am building the symbols package. I forgot to write for you to tick this in my steps. My mistake.
The settings pointing to the src code is filled out. But has no effect.
Once again this issue is isolated to the android emulator and VS nuget (with symbols) debugging.
Sorry, the steps seem a bit vague to me... Did you take a look at the two links? You're doing what they suggest already?
@generik0 I do think it's best if you could make a quick reproduction project, so we can look into this further.
We actually don’t build in release mode. Build in Debug ;-) and in .net standard the default when building package in debug appears to be portable now.
My colleague will double this check. Let me get back to us...