Nils Lehnen f8ffccae7f Use InvariantCulture when parsing machine-generated dates ... DateTime.TryParse without an IFormatProvider falls back to the current thread culture, so the same string can parse differently (or fail) depending on the server's locale. None of these call sites deal with user-entered text - they parse dates that come from filenames, an HTTP header, ffprobe metadata and values the app itself wrote to the auth database - so InvariantCulture is the correct provider everywhere here. Fixes the S6580 / CA1305 warnings on these call sites. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-04 23:55:31 +02:00
..
CodecType.cs
FFProbeHelpers.cs	Fix duplicate key collision	2026-06-12 11:44:26 -04:00
InternalMediaInfoResult.cs	Improve dynamic HDR metadata handling (#13277)	2025-04-02 18:06:02 -06:00
MediaChapter.cs
MediaFormatInfo.cs
MediaFrameInfo.cs	Improve dynamic HDR metadata handling (#13277)	2025-04-02 18:06:02 -06:00
MediaFrameSideDataInfo.cs	Improve dynamic HDR metadata handling (#13277)	2025-04-02 18:06:02 -06:00
MediaStreamInfo.cs	Only set IsAvc for video streams	2026-03-29 14:27:49 +02:00
MediaStreamInfoSideData.cs
ProbeResultNormalizer.cs	Use InvariantCulture when parsing machine-generated dates	2026-07-04 23:55:31 +02:00