EngineeringUnits
EngineeringUnits copied to clipboard
UnitsNet version
What version of UnitsNet is this library based on? UnitsNet 6.0.0-pre013 is currently being developed, is the syntax and functionality compatible with this version? And the use of IQuantity?
Hi @EarlJester
When we started this project 2-3 years ago UnitsNet and EngineeringUnits shared 100% syntax and functionality.
But after this point we have not tried to add any new functionality that UnitsNet had created so I dont really know anymore how comparable the two systems are.
Have you had problems converting from UnitsNet to EngineeringUnits?
Good afternoon, thank you, I'm waiting.
Yes, now the key functionality of Units.Net is Quantity. This allows you to work flexibly with quantities, and scale physical quantities without being tied to specific quantities types.
In EngineeringUnits, the old version of UnknownType is used. Not to mention the different syntax, UnknownType is a simpler and stripped-down version, which does not allow you to use EngineeringUnits and requires manual revision of the library and adding the functionality implemented in Units.Net.
At the moment, I see it as optimal to use Units.Net for storage, conversion and as the core of quantities, and EngineeringUnits as a calculation library in the necessary places. But in this case, similar syntax already acts as an obstacle to convenient work for the developer due to confusion in namespaces.
@MadsKirkFoged found this nuget right now and trying to decide between boths here mentioned. My external API returns me a string representing the unit, no Type or similar, just a string. Maybe you could check on this again and come back with an answer?