[System.Management] Skip DateTime_RoundTrip test for corefx implementation

[Yoticc]

Contributing towards #118321

Added a check for the framework version to avoid a test that is known in advance to fail for the .netstandard target.

Regarding the additional condition check besides ActiveIssue, I noticed that xunit-console does not recognize the attribute and launches the test. Therefore, a separate condition check is required.

[kasperk81]

[System.Management] Skip DateTime_RoundTrip test for corefx implementation

corefx is the name of .NET Core Libraries, you want to say .NET Framework implementation

Regarding the additional condition check besides ActiveIssue, I noticed that xunit-console does not recognize the attribute and launches the test. Therefore, a separate condition check is required.

what about the other 2k usages of [ActiveIssue] in the repo? you shouldn't care for it in this single instance

[Yoticc]

corefx is the name of .NET Core Libraries, you want to say .NET Framework implementation

You are right, it is worth changing the term "corefx" to ".NET Framework". I was mistaken in my comment. Initially, it pointed to the root of the issue, which lay in corefx repository.

what about the other 2k usages of [ActiveIssue] in the repo? you shouldn't care for it in this single instance

I believe this is a good practice. Removing the ActiveIssueAttribute and leaving the exception seems like a bad idea because it leaves no reference to the issue.
Rather, the question is how appropriate it is to mark "permanent issue for unsupported target" using ActiveIssue, which is intended for temporary test skipping. It would be helpful to hear the member's opinion on the best practice.
Perhaps it should be replaced with a simple comment containing the issue ID or link.

[kasperk81]

I believe this is a good practice. Removing the ActiveIssueAttribute and leaving the exception seems like a bad idea because it leaves no reference to the issue.

i was suggesting to do the opposite, remove the excessive condition

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-management
See info in area-owners.md if you want to be subscribed.