We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since we have task assembly load context checked in. We should be able to produce such Task easily and consume them with just a package reference.
The implementation code will probably be in SDK. And share a big chuck with PackAsTool=true
The text was updated successfully, but these errors were encountered:
We should have a template and something like dotnet build /p:packAsTask=true
and one the consumer side just add a package reference. And you can use the target maybe even without <using....>
Sorry, something went wrong.
Do you mean this #4834?
I don't think that's the same
Ahhh... Similar to SDKs but only with UsingTask in the imports. I see now.
UsingTask
Projects like MSBuild Extension Pack and many others would benefit from this.
MSBuild Extension Pack
Having a project system to author, debug and test MSBuild packages would complement this.
I think this could be rolled into #7548.
No branches or pull requests
Since we have task assembly load context checked in. We should be able to produce such Task easily and consume them with just a package reference.
The implementation code will probably be in SDK. And share a big chuck with PackAsTool=true
The text was updated successfully, but these errors were encountered: