[Breaking change]: Respect DebugSymbols=false #41400
Labels
breaking-change
Indicates a .NET Core breaking change
🏁 Release: .NET 8
Work items for the .NET 8 release
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
Pri1
High priority, do before Pri2 and Pri3
📌 seQUESTered
Identifies that an issue has been imported into Quest.
Description
Our documentation says that DebugSymbols=false, when specified from the command line, means we won't output pdbs. That isn't currently true, and we don't know for how long that hasn't been true. This changes it such that that is now true: DebugSymbols=false suppresses pdb generation by changing DebugType to None.
Customers who currently have a script that includes -p:DebugSymbols=false may currently be expecting pdbs to be created because that is current behavior, and that will change with this.
Version
.NET 8 GA
Previous behavior
-p:DebugSymbols=false did not suppress pdb generation.
New behavior
-p:DebugSymbols=false now suppresses pdb generation.
Type of breaking change
Reason for change
This aligns with our documentation and user expectations. It has led to confusion in the past.
Recommended action
If a user wants to generate pdbs, do not specify -p:DebugSymbols=false on the command line. Simply remove that property, and they will be generated again.
Feature area
SDK
Affected APIs
N/A
Associated WorkItem - 286584
The text was updated successfully, but these errors were encountered: