Stub tasks that are not supported on .NET#9153
Merged
rainersigwald merged 11 commits intodotnet:mainfrom Sep 27, 2023
Merged
Conversation
Contributor
Author
|
I added a |
Member
rainersigwald
left a comment
rainersigwald
left a comment
There was a problem hiding this comment.
The strategy looks good--a few nits mentioned below, but I'm ok with adding the CP0007 exceptions for this, once the classes are static.
Contributor
Author
Did you mean |
Member
Sure did! |
rainersigwald
approved these changes
Sep 27, 2023
Member
rainersigwald
left a comment
rainersigwald
left a comment
There was a problem hiding this comment.
Thanks for keeping this up to date. We'll be taking a bunch of PRs now that we've forked for .NET 8/VS 17.8.
bulatgrzegorz
pushed a commit
to bulatgrzegorz/selective-condition-evaluator
that referenced
this pull request
Oct 16, 2023
Following the pattern used for the `ResolveComReference` task, create stubs for .NET that provide a clear error message indicating the task is not supported on .NET. Fixes dotnet#3499.
This was referenced Jul 29, 2025
Closed
Closed
This was referenced Oct 26, 2025
This was referenced Nov 13, 2025
Closed
Open
This was referenced Nov 22, 2025
Closed
This was referenced Dec 1, 2025
This was referenced Dec 9, 2025
Open
This was referenced Dec 24, 2025
This was referenced Jan 30, 2026
This was referenced Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3499
Context
Following the pattern used for the
ResolveComReferencetask, create stubs for .NET that provide a clear error message indicating the task is not supported on .NET.Changes Made
The following tasks have been updated:
ALAspNetCompilerGenerateBootstrapperGenerateTrustInfoGetFrameworkSdkPathRegisterAssemblyResolveComReferenceResolveNativeReferenceUnregisterAssemblyUpdateManifestWinMDExpAdditionally, the Utilities project has been updated so thatAppDomainIsolatedTask(base class ofAppDomainIsolatedTaskExtensionand a dependency ofResolveComReference) is included for '.NETFramework' only.Testing
Tested on macOS and Windows 11 with test project files (attached as TaskTest.zip.)
Notes
I don't have a full understanding of the interactions of the preprocessor symbols. (e.g. Is
FEATURE_APPDOMAINonly valid forNETFRAMEWORK?) There may be improvements that can be made to the conditionals in the source and in the .targets file.Should unit tests be added for the stubs?