You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question out of interest: why is XamlStyler sticking with NewtonSoft.JSON now that System.Text.JSON is available?
Visual Studio uses Newtonsoft.Json internally and ships with a version. Having extensions ship with a different version of Json.NET can cause hard to debug issues.
Obviously, XamlStyler works with more than just VS, but using different serialization libraries in different versions of the tool would introduce new complexities.
Why not remove Json.NET entirely? I assume it comes down to not wanting to create work with no immediate benefit (other than supporting installation on older VS versions).
After publishing final feature update supporting VS2017 (#480), we will be unblocked form updating Newtonsoft.Json to version 12.0.2. More information here: Using Newtonsoft.Json in a Visual Studio extension.
The text was updated successfully, but these errors were encountered: