2024-04-15T14:54:36.0000000Zhttps://world.optimizely.com/blogs/sheider-devnotes/ Optimizely World <p>Hey all,</p> <p>First post here and I would like to talk about Timezone ID's and How Windows and Linux systems use different IDs.</p> <p>We currently run a .NET Core site with Opti CMS and Customized Commerce (B2B Commerce) all hosted in DXC. And with our solution we had an automated process of what would be a scheduled publish of our commerce items.</p> <p>We identified we had issues where our commerce items would publish early. Our investigation found that if you are using Timzezone ID's or just using the OOB TimeZoneInfo, the results you get will vary from your local development in windows to where its deployed to, in our case DXC (Linux).</p> <p>With this in mind, we had to find a conversion nuget that would allow us to enter a windows timezone ID and allow it to auto convert it based on the environment it was deployed to.</p> <p><a href="https://github.com/mattjohnsonpint/TimeZoneConverter">https://github.com/mattjohnsonpint/TimeZoneConverter</a> is the conversion nuget we use.</p> <p>**Notes to those on .net 6+ from that Repository listed above:</p> <p><span>.NET 6 has built-in support for IANA and Windows time zones in a cross-platform manner, somewhat reducing the need for this library. It relies on&nbsp;</span><a href="https://docs.microsoft.com/dotnet/core/extensions/globalization-icu">.NET's ICU integration</a><span>&nbsp;to perform this functionality. See&nbsp;</span><a href="https://devblogs.microsoft.com/dotnet/date-time-and-time-zone-enhancements-in-net-6/#time-zone-conversion-apis">the .NET blog</a><span>&nbsp;for details.</span></p> <p><span>I Hope this information is useful to those of you who are working in .Net Core and are having issues with scheduled publish discrepencies.</span></p> <p><span>Cheers,</span></p> <p><span>Sean Heider</span></p>2024-04-15T14:54:36.0000000Z

Blog post