--
---
You received this message because you are subscribed to the Google Groups "Noda Time" group.
To unsubscribe from this group and stop receiving emails from it, send an email to noda-time+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/noda-time/b8599e66-834d-448e-ab5d-9299a0f50eb8n%40googlegroups.com.
Thanks for the quick reply.I'm interesting in running TzdbCompiler directly so that I can use Noda Time in a Continuous Integration pipeline, to run my validation tests as soon as a new IANA TZDB version drops, instead of waiting for a new release of Noda Time.
Once that works well, I want to point the TzdbCompiler directly at the unreleased TZDB files at https://github.com/eggert/tz, and run the CI on the unreleased TZDB to catch errors before a new release is created. (It looks like TzdbCompiler just needs a small tweak to ignore the missing Version.)
With regards to a PR to fix this, do you have a pointer where I should start? Because I started using C# and .NET just 4 days ago... Translating from Java to C# was relatively straightforward, but I have basically no knowledge of the .NET environment (I find it hard enough to just track the terminology: ".NET Core", ".NET Standard", ".NET Framework"??).
Are you aware that typically a new .nzd file is published on https://nodatime.org within a few hours of the announcement of new data, and a new release of Noda Time alongside that? If you ever need to wait more than 12 hours, that's almost certainly because there's something in the data which is causing a problem for the TzdbCompiler. That won't help with your next aim, admittedly.
Once that works well, I want to point the TzdbCompiler directly at the unreleased TZDB files at https://github.com/eggert/tz, and run the CI on the unreleased TZDB to catch errors before a new release is created. (It looks like TzdbCompiler just needs a small tweak to ignore the missing Version.)Right... that sounds okay, but I wouldn't want to end up with more work due to issues found within the unreleased data, which might then be reverted again.
With regards to a PR to fix this, do you have a pointer where I should start? Because I started using C# and .NET just 4 days ago... Translating from Java to C# was relatively straightforward, but I have basically no knowledge of the .NET environment (I find it hard enough to just track the terminology: ".NET Core", ".NET Standard", ".NET Framework"??).Well you could try specifying multiple frameworks in the project file, with <TargetFrameworks> instead of <TargetFramework>. The frameworks should be semi-colon-separated (so <TargetFrameworks>netcoreapp3.1;net5.0</TargetFrameworks>).I don't know off-hand what that will do in terms of running without specifying a framework.
--
---
You received this message because you are subscribed to the Google Groups "Noda Time" group.
To unsubscribe from this group and stop receiving emails from it, send an email to noda-time+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/noda-time/8f1960d7-27c3-4206-b932-32a908b9d5ebn%40googlegroups.com.