Skip to content

use some pattern matching #6045

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.

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

Closed

Conversation

SimonCropp
Copy link
Contributor

this is purely a personal preference

Youssef1313
Youssef1313 previously approved these changes Jul 16, 2025
# Conflicts:
#	src/Analyzers/MSTest.SourceGeneration/Helpers/SystemPolyfills.cs
#	src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs
Youssef1313
Youssef1313 previously approved these changes Jul 16, 2025
@Evangelink
Copy link
Member

@SimonCropp what's the proper fix for:

.packages/polyfill/9.0.0-beta.14/build/Polyfill.targets(69,5): error PolyfillTargetsForNuget: (NETCORE_ENGINEERING_TELEMETRY=Build) Projects that produce a nuget and consume Polyfill:
For best performance all frameworks from the lowest TargetFramework up to and including net48 should be targeted.
For example:
 * If a nuget's minimum target is net47, then the resulting TargetFrameworks should include net471, net472, and net48.
 * If a nuget's minimum target net6, then the resulting TargetFrameworks should include net7.0 and net8.0.

@@ -46,6 +48,7 @@ This package provides the C# source generators for MSTest test framework.]]>
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<!-- Analyzers to help write analyzers/generators -->
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
<PackageReference Include="Polyfill" PrivateAssets="all" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is likely to cause us issues, if not now, later. This project targets netstandard2.0 and has IVT exposed to test project (not netstandard2.0). So likely going to cause us issues, unless either IVT is removed and make the needed members public, or EmbeddedAttribute is used.

@SimonCropp
Copy link
Contributor Author

@Evangelink
Copy link
Member

Closing this one too for now, we need to wait for the EmbeddedAttribute feature.

@Evangelink Evangelink closed this Jul 22, 2025
auto-merge was automatically disabled July 22, 2025 10:00

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants