Hi, Errors on compile native libs again - sorry π
Visual studio 18.5.3.
And so on...
constants.hpp:

last modified on 29.10.2025π€·ββοΈ
Still, it seems to me that the problem is that databento-dotnet doesn't reference a specific databento-cpp release/commit/tag, but instead pulls in the main branch every time (current commit 40c5a7ba8466561c1a774f6bd72fe05fc1e3e5df - v0.57.0). Some breaking changes occur there, and the build stops working. Of course, I could be wrong... π€
But in any case, I think it's best to have a link to a specific databento-cpp release for the databento-dotnet release. This way, you can understand what functionality is available/implemented. Especially considering that breaking changes are introduced into databento-cpp quite often.
------------------------------UPD------------------------------
Yes, I was right - with databento-cpp v0.52.0 all builds fine.
Hi, Errors on compile native libs again - sorry π
Visual studio 18.5.3.
And so on...

constants.hpp:last modified on 29.10.2025π€·ββοΈ
Still, it seems to me that the problem is that
databento-dotnetdoesn't reference a specificdatabento-cpprelease/commit/tag, but instead pulls in themainbranch every time (current commit40c5a7ba8466561c1a774f6bd72fe05fc1e3e5df-v0.57.0). Some breaking changes occur there, and the build stops working. Of course, I could be wrong... π€But in any case, I think it's best to have a link to a specific
databento-cpprelease for thedatabento-dotnetrelease. This way, you can understand what functionality is available/implemented. Especially considering that breaking changes are introduced intodatabento-cppquite often.------------------------------UPD------------------------------
Yes, I was right - with
databento-cppv0.52.0all builds fine.