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
The nuget package's Microsoft.VisualStudio.Shared.VSCodeDebugProtocol project URL lists this repo as its homepage, so that's why I'm reporting the issue here.
The MIEngine, used by the vscode-cpptools extension, changes the to-be-debugged application's CLI args if they contain ISO 8601 strings. I have boiled down this issue of MIEngine using the default behavior of the Newtonsoft.Json library. For whatever reason, it sometimes parses strings as date objects, which may serialize to a different string than originally used.
MIEngine seems to use Microsoft.VisualStudio.Shared.VSCodeDebugProtocol for parsing the JSON document, leaving no room for adjusting the JSON parser's behavior by itself.
I investigated the Microsoft.VisualStudio.Shared.VSCodeDebugProtocol package and came to the conclusion that Microsoft.VisualStudio.Shared.VSCodeDebugProtocol.Protocol.DebugProtocol might needed to be modified to include the DateParseHandling = DateParseHandling.None setting in its jsonSettings.
However, I'm not sure if this is sufficient to fix the issue everywhere because I cannot find the source code to that package to verify it.
The nuget package's
Microsoft.VisualStudio.Shared.VSCodeDebugProtocol
project URL lists this repo as its homepage, so that's why I'm reporting the issue here.The
MIEngine
, used by thevscode-cpptools
extension, changes the to-be-debugged application's CLI args if they contain ISO 8601 strings. I have boiled down this issue ofMIEngine
using the default behavior of theNewtonsoft.Json
library. For whatever reason, it sometimes parses strings as date objects, which may serialize to a different string than originally used.MIEngine
seems to useMicrosoft.VisualStudio.Shared.VSCodeDebugProtocol
for parsing the JSON document, leaving no room for adjusting the JSON parser's behavior by itself.I investigated the
Microsoft.VisualStudio.Shared.VSCodeDebugProtocol
package and came to the conclusion thatMicrosoft.VisualStudio.Shared.VSCodeDebugProtocol.Protocol.DebugProtocol
might needed to be modified to include theDateParseHandling = DateParseHandling.None
setting in itsjsonSettings
.However, I'm not sure if this is sufficient to fix the issue everywhere because I cannot find the source code to that package to verify it.
Related issues:
The text was updated successfully, but these errors were encountered: