Could you please review this page and make sure that it is actually correct? Because there are a few posts that claim that parts of that documentation is wrong or outdated.
A good starting point is this question on StackOverflow. The two highest voted answers both say that this documentation is outdated and they also provide links to further information.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks, @cremor, for your feedback. We'll have to investigate before we can revise the documentation.
https://github.com/dotnet/roslyn/blob/master/docs/compilers/CSharp/CommandLine.md has up to date documentation of the switch.
The current doc is missing /debug:portable and /debug:embedded descriptions.
The other key change i that /debug:pdbonly should be called out as a Windows only debug format. The /debug:portable would be preferred.
Also /debug:pdbonly is exactly the same as /debug:full. It's not really a Windows-only switch.
It will produce Portable PDB on Linux and Windows PDB on Windows.
You can link https://github.com/dotnet/designs/blob/master/accepted/diagnostics/debugging-with-symbols-and-sources.md#pdb-formats that discusses the PDB formats.
Azure function c# Visual studio 2017, debugging locally, fine, remote debugging: 'no symbols have been loaded...' crap when I try to set up break, point ! Have tried various debug options with no results..
enfuriating !!!
Oh, and this only happens when using V2 fuctions and .net code, V1 functions, remote debugging works fine
This documentation is still out of sync because the newly added options such as embedded, portable are not updated while there are external documentation that describes this. It will be good to capture the same information in this page as well
@IEvangelist this page is massively out of date and wrong.