-
Notifications
You must be signed in to change notification settings - Fork 83
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
Dont use IndexOf as that has Cuture issues #563
base: main
Are you sure you want to change the base?
Conversation
Ah Contains dont work in all MSBuild versions, ie the one is used in CI here. |
Its easy for tooling to differentiate between a solution file and a project because they have different extensions. However, its much harder if two projects end in It is set after From the issue you linked, it looks more like not properly converting the Are you seeing issues because of this call to |
Yes in this case its because of the call to |
I'm a little nervous about changing behavior. Would comparing a string work better? - <IsTraversal Condition=" '$(IsTraversal)' == '' And $(TraversalProjectNames.IndexOf($(MSBuildProjectFile), System.StringComparison.OrdinalIgnoreCase)) >= 0 ">true</IsTraversal>
+ <IsTraversal Condition=" '$(IsTraversal)' == '' And '$(TraversalProjectNames.IndexOf($(MSBuildProjectFile), System.StringComparison.OrdinalIgnoreCase))' != '0' ">true</IsTraversal> |
@jeffkl - good idea, that seem to work as well, so im changing the code to do that instead |
Using string seem to solve this issue for now
7b25c2b
to
bb8e241
Compare
Theres currently some culture issues using IndexOf as mentioned in this issue dotnet/msbuild#5502.
dotnet/msbuild#5502 fixes it, but its only enabled in a late wave, that we are not depending on yet.
This PR uses contains instead, it seem that fixes the issue with Culture for now.