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
Fix for Issue #13339 cause MS Visual Studio 2015 to always fail configuration for cpp plugin #20968
Comments
Sorry for the late reply. Sorry that you're having trouble with Gradle! We appreciate the effort that went into filing this issue, but we must ask for more information. As stated in our issue template, a minimal reproducible example is a must for us to be able to track down and fix your problem efficiently. Our available resources are severely limited, and we must be sure we are looking at the exact problem you are facing. If we have a reproducer, we may be able also to suggest workarounds or ways to avoid the problem. The ideal way to provide a reproducer is to leverage our reproducer template. You can also use Gradle Project Replicator to reproduce the structure of your project. This issue will be closed after 7 days unless you provide more information. Please, provide all the steps required to reproduce this and all relevant environment details |
To reproduce the problem:
|
@epxilinx Why do you think that this is a problem caused by Gradle and not VS2015? |
@ov7a is VS2015 supported by gradle? vswhere utf8 commit: microsoft/vswhere@2444e2e |
We don't have plans to support VS2015. |
The changes in #15975 add the
vswhere
argument-utf8
which is not support by VS 2015 vswhere.exe version. Workaround is to manually install updated version of vswhere. Note that I cannot update MSVS version due to company restrictions.Expected Behavior
Configuration of project that uses cpp application plugin should pass or at least fail with message indicating vswhere needs to be updated.
Note that there is an "ignoring" message when vswhere returns non-zero but it quickly results in a NPE. Failing with a meaningful vswhere exit code would have been a preferable error state.
Current Behavior
Direct call to vswhere:
The text was updated successfully, but these errors were encountered: