Description

We used to always set ToolCommandName for projects when packaged or built, regardless of whether or not they were a tool package. Now we only set it if PackAsTool is true and the package is a tool. Users may be surprised that this property is no longer set.

Please read the conversation in dotnet/sdk#51739

Version

.NET 10 RC 1

Previous behavior

ToolCommandName was always set.

New behavior

ToolCommandName is only set if its a tool package project.

Type of breaking change

• Binary incompatible: Existing binaries might encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
• Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code might require source changes to compile successfully.
• Behavioral change: Existing binaries might behave differently at run time.

Reason for change

ToolCommandName does not make sense for non tool projects.

Recommended action

If you rely on this being set, please set the property explicitly or convert your project to a tool.

Feature area

SDK

Affected APIs

No response

Associated WorkItem - 537286