Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 9 commits
- 14 files changed
- 3 contributors
Commits on Feb 23, 2023
-
-
Bump Devlooped.SponsorLink from 0.9.6 to 0.9.7
Bumps [Devlooped.SponsorLink](https://github.com/devlooped/SponsorLink) from 0.9.6 to 0.9.7. - [Release notes](https://github.com/devlooped/SponsorLink/releases) - [Changelog](https://github.com/devlooped/SponsorLink/blob/main/releases.md) - [Commits](https://github.com/devlooped/SponsorLink/commits) --- updated-dependencies: - dependency-name: Devlooped.SponsorLink dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
-
Bump Microsoft.NET.Test.Sdk from 17.4.1 to 17.5.0
Bumps [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest) from 17.4.1 to 17.5.0. - [Release notes](https://github.com/microsoft/vstest/releases) - [Changelog](https://github.com/microsoft/vstest/blob/main/docs/releases.md) - [Commits](microsoft/vstest@v17.4.1...v17.5.0) --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Commits on Feb 24, 2023
-
Allow extending the build with local-only targets
These are always ignored and can therefore be tweaked without fear of inadvertently checking them in.
-
Render nuspec as a relative path to the nugetize output
This makes it easier to take screenshots without revealing full local paths, while still preserving the click-ability of those file links if the terminal supports it.
-
Ensure transitive dependencies are properly resolved for inference
.NET 7.0 SDK changed from: ```xml <ResolvePackageDependencies ProjectPath="$(MSBuildProjectFullPath)" ProjectAssetsFile="$(ProjectAssetsFile)" ProjectLanguage="$(Language)" EmitLegacyAssetsFileItems="$(EmitLegacyAssetsFileItems)" TargetFramework="$(TargetFramework)" ContinueOnError="ErrorAndContinue"> <Output TaskParameter="PackageDefinitions" ItemName="PackageDefinitions" /> <Output TaskParameter="PackageDependencies" ItemName="PackageDependencies" /> <!-- These outputs only produced when EmitLegacyAssetsFileItems is true --> <Output TaskParameter="TargetDefinitions" ItemName="TargetDefinitions" /> <Output TaskParameter="FileDefinitions" ItemName="FileDefinitions" /> <Output TaskParameter="FileDependencies" ItemName="FileDependencies" /> </ResolvePackageDependencies> ``` to: ```xml <ResolvePackageDependencies ProjectPath="$(MSBuildProjectFullPath)" ProjectAssetsFile="$(ProjectAssetsFile)" ProjectLanguage="$(Language)" TargetFramework="$(TargetFramework)" ContinueOnError="ErrorAndContinue" Condition="'$(EmitLegacyAssetsFileItems)' == 'true'"> <Output TaskParameter="PackageDefinitions" ItemName="PackageDefinitions" /> <Output TaskParameter="PackageDependencies" ItemName="PackageDependencies" /> <Output TaskParameter="TargetDefinitions" ItemName="TargetDefinitions" /> <Output TaskParameter="FileDefinitions" ItemName="FileDefinitions" /> <Output TaskParameter="FileDependencies" ItemName="FileDependencies" /> </ResolvePackageDependencies> ``` Since the SDK now conditions the execution of the resolve to the value of `EmitLegacyAssetsFileItems`, we need to explicitly set it. Since this was likely done for performance reasons, only turn on when package inference is active, since we don't use that anywhere else.
Commits on Feb 25, 2023
-
Bump Microsoft.TestPlatform.ObjectModel from 17.4.1 to 17.5.0
Bumps [Microsoft.TestPlatform.ObjectModel](https://github.com/microsoft/vstest) from 17.4.1 to 17.5.0. - [Release notes](https://github.com/microsoft/vstest/releases) - [Changelog](https://github.com/microsoft/vstest/blob/main/docs/releases.md) - [Commits](microsoft/vstest@v17.4.1...v17.5.0) --- updated-dependencies: - dependency-name: Microsoft.TestPlatform.ObjectModel dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
-
Pack console apps using publish output by default
We have an SDK-compatible mechanism for packing .NET tools: PackAsTool. This satisfies a very specific scenario for .NET tools, but doesn't work for regular CLI tools that don't need packing as standalone dotnet tools. For these CLI tools, packing the output of Publish makes much more sense, and results in way fewer customizations in package references. We introduce a new property, PackAsPublish, which is initialized to `true` whenever the project is publishable and a cross-platform executable (pending widening the definition upon feedback). In this case, we don't infer content from package dependencies and references with copy local and so on, but rather rely exclusively on Publish doing its work. We don't change the PackFolder treatment, so that property is orthogonal to PackAsPublish, although it's likely `tools` will be the most commonly used folder. The property's default `true` value is calculated dynamically in an initial target since we need to inspect `ProjectCapability` which is set by the SDK to include `CrossPlatformExecutable`. This is the more extensible approach, rather than checking the output type ourselves.
-
There are no files selected for viewing