Skip to content

disable package validation for .NET tools #50941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 22, 2025
Merged

disable package validation for .NET tools #50941

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.PackTool.targets
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,14 @@ NOTE: This file is imported from the following contexts, so be aware when writin
AssemblyFile="$(MicrosoftNETBuildTasksAssembly)" />

<PropertyGroup>
<!-- tools are specially-formatted packages, so we tell nuget Pack to not even try to include build output -->
<!-- Tools are specially-formatted packages, so we tell nuget Pack to not even try to include build output.
Since this file is only loaded when PackAsTool is true, we can safely disable validation here. -->
<IncludeBuildOutput>false</IncludeBuildOutput>

<!-- Tool packages are not library/API-providing packages, so they should not participate in API Compat validation at all.
Since this file is only loaded when PackAsTool is true, we can safely disable validation here. -->
<EnablePackageValidation>false</EnablePackageValidation>

<!-- Determine information about all of the potential tool packages to build -->
<!-- If shims are included, we need to make sure we restore for those RIDs so the apphost shims are available during restore/publish.
This means that we need to set RuntimeIdentifiers. However we need to track certain information about the _users_ decisions around RIDs
Expand Down
Loading