-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cannot change certain Editor.Options when the TestApp is compiled with .NET Native toolchain #49
Comments
There is some rd.xml madness going on and I could not find any clue in the documentation on how to solve this. [JsonProperty("lineNumbers", NullValueHandling = NullValueHandling.Ignore)]
string LineNumbers { get; set; } |
Thanks for digging in and finding the cause @WelterDevelopment. There may be some rd.xml stuff we can do in the component, I'll have to take a look. |
I've added toggling this option in the sample app. I can see what you see in Release mode that it's updating on the C# side, but then just being turned off in the Monaco editor (and never turning back on); even though it's fine in Debug. It's fine up until the point of serialization. I'm going to try debugging on the script side now to see what might be going on there on the receiving end to confirm. |
Ok, from the script side it's still getting called to update, but in Debug it's getting passed the string value like "on", "off", "relative", etc... In Release mode it's being passed an int like 0, 1, 2 instead... 🤔 |
For whatever reason it seems like Json.NET can't infer the |
…onverter when running in .NET Native No idea why the existing declaration on the interface isn't being used/picked-up properly and ignored by Json.NET... config issue or quirk?
Steps to reproduce:
This issue also occurs e.g. with Editor.Options.WordWrap and maybe even for more Editor.Options. I have not tested them all.
And turning off the .NET Native Compiler is of course not an option since all UWP apps you want to submit to the Microsoft Store need to be compiled with this toolchain.
The text was updated successfully, but these errors were encountered: