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 QP timestamps in the binding configuration file are not stored in UTC format, and so change each time the binding is updated by a machine in a different timezone.
Note: SLVS is correctly detecting that the timestamps are equivalent i.e. it is not incorrectly reporting that the QP has been updated and needs to be changed.
However, it is generating an irritating and potentially confusing change to the file in source control.
See this community issue. The thread relates to legacy connected mode (.sqconfig files) but also applies to the new connected mode format (.slconfig).
Repro steps
Bind a solution
Close VS
Change the machine time-zone to one with a different offset from UTC
Re-open the solution in VS
Update the binding
Expected behavior
The timestamps in the binding config file should not change.
Actual behavior
The timestamps in the binding config file should change to reflect the same time in new timezone.
Known workarounds
None.
Related information
SonarLint for VS Version: v4.15 (and earlier)
The text was updated successfully, but these errors were encountered:
Description
The QP timestamps in the binding configuration file are not stored in UTC format, and so change each time the binding is updated by a machine in a different timezone.
Note: SLVS is correctly detecting that the timestamps are equivalent i.e. it is not incorrectly reporting that the QP has been updated and needs to be changed.
However, it is generating an irritating and potentially confusing change to the file in source control.
See this community issue. The thread relates to legacy connected mode (.sqconfig files) but also applies to the new connected mode format (.slconfig).
Repro steps
Expected behavior
The timestamps in the binding config file should not change.
Actual behavior
The timestamps in the binding config file should change to reflect the same time in new timezone.
Known workarounds
None.
Related information
The text was updated successfully, but these errors were encountered: