# featbench / conan-io__conan-17076 - taskset: [featbench](https://harnessreport.com/tasks/featbench.md) - difficulty: hard - category: feature - language: - runnable from the site: no - agent timeout: 4800s ## Results by harness _none yet_ ## Instruction ``` I want to be able to customize the configuration and platform condition keys used in MSBuildDeps property sheets when working with large Visual Studio solutions in monorepos. Currently, when I have a solution with hundreds of projects and use a dedicated conan project to manage dependencies, I face issues when different projects in the same solution use different build configurations. The property sheets generated by Conan need to match the configuration variables used in my project files for proper import. I need to specify custom names for the Configuration and Platform variables that MSBuildDeps uses when generating the condition statements in the property sheets. This will allow me to align the property sheet conditions with the variable names used in my Visual Studio project files, ensuring that the correct property sheets are imported based on my project's specific configuration settings. Specifically, I want to be able to: - Set a custom configuration key name instead of the default "Configuration" value - Set a custom platform key name instead of the default "Platform" value - Have these custom key names used in both the condition statements and the property sheet filenames - Maintain backward compatibility by keeping the default values when I don't specify custom ones This customization should work seamlessly with the existing MSBuildDeps functionality, allowing me to generate property sheets that correctly condition on my project's specific configuration and platform variable names. The solution should handle all the same build configurations and platforms as before, but with my chosen variable names in the condition statements. The outcome I expect is that when I build my Visual Studio solution with mixed configurations across different projects, the property sheets generated by Conan will properly match and import based on the custom configuration and platform variable names I've specified in my project files, eliminating the current mismatch issues. ``` --- Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp