Closed memsharded closed 5 months ago
very strange, we already have fixed such issue in the past: https://github.com/conan-io/conan-vs-extension/issues/77
This was an issue before, but now (v1.1.x
) we are checking for a property file with the same path before adding it to the project. Can you re-check the version you are using?
One more thing to try, just in case: what happens if I run Conan several times without waiting for a previous run to finish?
I experience the same problem (for your information, I'm using v1.2.2.346 from Visual Studio marketplace). If you run conan several times on the same project / solution, there is no problem, since it is checked that it not exists before adding it to project. Checked in this function: ConanService.IntegrateIntoConfiguration But, the check relies on Visual Studio property "VCConfiguration.PropertySheets" there
The problem appears when you delete conanbuildinfo.props (this could frequently append, since it's located in $(OutDir)). To reproduce the issue, do this:
I hope that it will help to find how to resolve this issue. Is it Microsoft responsibility, since Visual doesn't report this property sheet when it's not accessible?
Not sure how I got to this, but the final result is:
Probably it needs to check for existence to not repeat it