You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a developer using the library, I sometimes want to step into the library's code while debugging or working with the code in the IDE.
Currently, when I navigate to symbols, Visual Studio cannot find them and falls back to decompiling the DLL. This results in a source code that is not debuggable (breakpoints can't be set) nor complete (here we have no default values visible):
Instead, I would like to see a real source code after navigation:
Describe the solution you'd like
I think there are two good, alternative solutions to this problem:
Enable SourceLink to have metadata about GIT repo and git commit embedded in the library so that Visual Studio can find the relevant source files.
Generate PDB files with symbols and include them in the NuGet package. From my experience, this has somewhat broader compatibility with the IDEs than SourceLink. The downside is that NuGet package is slightly larger. And having symbols in a separate *.snupkg wasn't well supported in the repositories the last time I checked.
Describe alternatives you've considered
Alternatively, developers would need to clone the library's source code and reference it from their source code instead of the NuGet package.
Additional context
I wanted to experiment a bit and propose a concrete code change, but I'm not sure how NuGet packages are created in this repo. Is dotnet-gemini.nuspec is used at all? I'm not sure if the package is created from Visual Studio or with some commands...
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a developer using the library, I sometimes want to step into the library's code while debugging or working with the code in the IDE.
Currently, when I navigate to symbols, Visual Studio cannot find them and falls back to decompiling the DLL. This results in a source code that is not debuggable (breakpoints can't be set) nor complete (here we have no default values visible):
Instead, I would like to see a real source code after navigation:
Describe the solution you'd like
I think there are two good, alternative solutions to this problem:
Enable SourceLink to have metadata about GIT repo and git commit embedded in the library so that Visual Studio can find the relevant source files.
Generate PDB files with symbols and include them in the NuGet package. From my experience, this has somewhat broader compatibility with the IDEs than SourceLink. The downside is that NuGet package is slightly larger. And having symbols in a separate
*.snupkg
wasn't well supported in the repositories the last time I checked.Describe alternatives you've considered
Alternatively, developers would need to clone the library's source code and reference it from their source code instead of the NuGet package.
Additional context
I wanted to experiment a bit and propose a concrete code change, but I'm not sure how NuGet packages are created in this repo. Is
dotnet-gemini.nuspec
is used at all? I'm not sure if the package is created from Visual Studio or with some commands...The text was updated successfully, but these errors were encountered: