-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
error MSB4018: The "GetOutOfDateItems" task failed unexpectedly #4226
Comments
Do you have a repro for this? |
Did u ever fix this I am getting the same > |
I also get this issue. |
The task that's failing is part of the C++ SDK, which is not part of this repo. Can you please file Visual Studio Feedback to report the bug to that team? Please link the feedback item here so that others can find and upvote it. One thing that would likely be helpful in the bug report is the inputs to the task. Those are logged when the build verbosity is set to diagnostic. |
@macrolik9 I'm having the exact same issue. It doesn't help that the MSbuild error messages are so damn cryptic. This is probably causes by some VSinstaller gone wild (since it installs stuff in 2 or 3 places totally disregarding previously installed locations. Yikes!). |
I get this error on some projects and not on others... |
@TomzBench Can you please file Visual Studio feedback, ideally with the logs mentioned in #4226 (comment)? I'm going to close this because this failure appears to be caused by C++ tasks. |
Hey thanks @rainersigwald - It turns out my issue was related to my file path being too long! Apparently having path strings longer than 260 chars can be a problem on Windows. Good to know - I think it's good to leave this feedback here because I don't know how to use Visual Studio Feedback. I got this error using MSBuild via CMAKE.... |
@TomzBench you may also be interested in #53 (comment). |
@rainersigwald Awesome that this is fixed. Is a "preview" build considered a stable release? Or is there some time to wait until it's on a stable release? |
That post was a while ago; the fix is in all stable releases of Visual Studio 2019 (but still requires the OS-level opt-in and has the other caveats). |
Ok i'll try opting in and seeing if that fixes for me, thanks |
The text was updated successfully, but these errors were encountered: