--
---
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.
For more options, visit https://groups.google.com/d/optout.
Jon, no particular reason for doing it myself, except that, like before, I follow UserGuide and try to learn something on the go. Beside, I have no idea how to 'fetch' tzdb(version).nzd, and have just a minute ago figured it out how to download from 'latest.txt'.Thanks to your reply, I did managed to compile "my own" (lol) 'tzdb-2016d.nzd', but the downloaded-one has different naming convention - 'tzdb2016d.nzd'.Not to mention that now that I did succeeded to compile the ...2016d.nzd file, I have no idea what to do with it (how exactly to use it). Though I should not tell this aloud, since I have humiliated myself enough for today by cmd.exe-compiling from C:\. LOL. There says 'root' directory. LOL again. Yea, I know, project's root. Got it. (Though it took me a while.)In my project, I have installed (from NuGet pckg) NodaTime, but searching (via Windows Explorer) in my project's folders, there is no *.nzd file. So I guess tzdb is somewhere embedded.
If I would want (and I will) to use this 'tzdb2016d.nzd' file, where in my project (using VS 2015 Community) should I put it, for NodaTime to be able to use it?
My goal is to code astrology software, and 2 types of DateTime will be used:1) from user input, i.e. birth time - year-month-day hour-minute-second, and location (city/country), from which I then must extract time zone and possible DST2) 'now' time, i.e. now time in London (no matter where in the world is the user of software situated)I will also use SwissEphemeris (swedll32.dll; actually .NET port of it - SwissEphNet), which will get me planet's positions for that DateTime. I have 2 options - to get planet positions by local time (Julian day) or by UTC (also Julian day).Now I need to figure it out which DateTime to use - global (UTC) or local. I guess global would be the first choice.
Btw, is there any sample code for a following:- user would have to select the location of the event/birth - one of those from 'zone1970.tab' file (or closest one).
No, I that's Noda Time support for Dapper...
--