Activities of "johannes.schreiner"

It also works for me after using the fix you suggested - tested in VS2022. If I set a breakpoint into my code, then I can use "Step Into..." to step into ABP code. What does not work however is navigating to the code outside of debugging mode (e.g. using F12 go to definition) - VS will just show the decompiler output then

Seems like a major pain point for VS users that is not related to ABP in particular but applies to all libraries with sourcelink

Thank you very much for the prompt answer.

Can you maybe check with some of your colleagues using Visual Studio if they know a way to browse all sourcelink code? Based on this ticket, I assume it is currenlty not possible? https://github.com/dotnet/roslyn/issues/24349

hi

Because https://github.com/dotnet/sdk/issues/1458 you need to install https://www.nuget.org/packages/SourceLink.Copy.PdbFiles when we use the source link

Thanks, that resolves the issue - I tested with ABP community edition.

Two further points:

  • I now get the full debugging experience with Rider (I can navigate all the sources in Rider, it seems not to be working however in Visual Studio). Our company is not mandating the use of Rider and some developers are working with Visual Studio. I can step into your library code with Visual Studio, but I cannot do F12 go to definition - i think visual studio just does not support this for sourcelink? Are you aware of any working solution to navigate all source code and set breakpoints for Visual Studio?
  • I am currently evaluating ABP commercial. Which license do we need to purchase to have the same debugging experience? Will this be available with the Team license or only with the Business license?

As you can read in my initial question, I have sourcelink enabled and it works for other packages. Can you please elaborate on why it could be that sourcelink does not work for ABP.

顯示 4 個紀錄的 1 到 4 個.
Made with ❤️ on ABP v8.2.0-preview Updated on 3月 25, 2024, 15:11