Jon Skeet

Okay, I've tracked this down to https://github.com/atsushieno/alsa-sharp/issues/2.

At a *guess*, that means that Microsoft is returning HTML rather than JSON... that's normally what "I was trying to parse JSON but I got `

Summary of discussions: - Try to reword to avoid the brackets - Avoid using "stream" in normative text, but have a note - Merge the "Asynchronous stream creation and usage"...

The answer is basically the same though: it would be a breaking change, and one we basically wouldn't take unless we moved to a new major version, which is rather...

I don't think Json.NET is going anywhere though. Making a breaking change and releasing a new major version feels like it would be significantly disruptive. I don't think it's worth...

I think we should address the detailed supported framework timelines in a separate issue, keeping this one to the Newtonsoft.Json dependency. However, I wouldn't expect to create a new major...

No solution is going to be perfect for everyone - but given that these libraries *are* in maintenance mode, I don't regard this as a *critical* issue. I guess in...

@guillaume86: Please could you file a new issue with the details of what you're trying to achieve, and why it needs new attributes to be applied? It sounds like it's...

@guillaumejay: As I noted on that issue, it's a problem with `dotnet publish`/`dotnet deploy`, and there's a fairly simple workaround. I'm not going to start making breaking changes because some...

@jamiehankins: Here are three different ways in which this would be a breaking change: - It would break the build of anyone who uses Newtonsoft.Json in their own code, but...