Fix OrderableString resolving

Updating a value on an OrderableString using the index accessor, like if it was a simple IList, can lead to duplicated value into the underlying _list member.
And if the resolved string doesn't have the same order value than  the already existing one, it will lead to annoying error at generation time.

We fix it by using the SetOrRemoveAtIndex, which is specifically done for this kind of case

Author: Vincent Bordenave

Sharpmake/Resolver.cs

@@ -812,6 +812,24 @@ private void ResolveMember(string objectPath, object obj, MemberInfo memberInfo,
                             SetResolved(memberPath);
                         }
                     }
+                    else if (fieldValue is OrderableStrings)
+                    {
+                        if (CanWriteFieldValue(fieldInfo))
+                        {
+                            SetResolving(memberPath);
+                            OrderableStrings values = fieldValue as OrderableStrings;
+
+                            for (int i = 0; i < values.Count; ++i)
+                            {
+                                bool wasChanged;
+                                string value = Resolve(values[i], fallbackValue, out wasChanged);
+                                if (wasChanged)
+                                    i = values.SetOrRemoveAtIndex(i, value);
+                            }
+
+                            SetResolved(memberPath);
+                        }
+                    }
                     else if (fieldValue is IList<string>)
                     {
                         if (CanWriteFieldValue(fieldInfo))