Closed MaxBen93 closed 1 year ago
@jonthysell Made some fixes for this awhile ago: https://github.com/search?q=repo%3Amicrosoft%2Freact-native-windows%20MSB4011&type=code What version are you on? If you're on an older version you can potentially take that spot fix.
Or is the problem that react-native-xaml specifically has a misconfigured property here?
@jonthysell Can you ensure that rn-xaml has the right configuration here?
All RN app and lib projects are expected to import, ExperimentalFeatures.props
, it's necessary so every project is "on the same page".
The "extra" import in JSEngine.props
was a workaround to support old module/app projects that havent updated to the latest template and don't have that nexessary import.
This was fixed in RN 0.71 with this commit: https://github.com/microsoft/react-native-windows/commit/492918196886cddef131fd1ec446a97c0c428693
It added a prop that could be set in your ExperimentalFeatures.props
file to prevent JSEngine.props
from importing it again.
Problem Description
When building
ReactNativeXaml.vcxproj
there is a warning being emitted due to a double-import ofExperimentalFeatures.props
This is likely because
ReactNativeXaml.vcxproj
does its own import of thatprops
file, while this is already being done byJSEngine.props
which is imported by way of existing RNW imports.If the order isn't important, this should be resolveable by removing the explicit import from
ReactNativeXaml.vcxproj
Steps To Reproduce
ReactNativeXaml.vcxproj
Expected Results
Clean output - free of errors and warnings.
Environment