-
Couldn't load subscription status.
- Fork 1.4k
Add message to to indicate which process exactly hold the lock for the file for task Generate*Manifest #9488
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
Conversation
|
Please retarget this PR to vs17.9 branch, since this isn't a new feature. |
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good; thanks!
Fixes #9465
Context
Unable to write manifest ‘obj\Debug\bc.exe.manifest’. The process cannot access the file ‘C:\Source\bc\bc\obj\Debug\bc.exe.manifest’ because it is being used by another process.
With limited error message, can't tell which process exactly hold the lock for the file.
Changes Made
use original the Copy task's "name the process that holds the lock" approach for the task GenerateManifestBase
Testing
Notes