axunonb

Actually I'm not yet satisfied with the current implementation, which is rather a POC. The response from SmartFormat users has been very low so far.

@Flithor In this case you should give `LogicCalcFormatter` a try. Just check-out the `pr-ncalc-formatter` branch. It's alive and rebased to the latest release. I'd appreciate hearing your comments. Have a...

Just updated NCalc package reference * NCalcSync v3.8.0 * Brutal.Dev.StrongNameSigner v3.4.0

@petero-dk @Flithor Currently this is a proof of concept. The necessary changes to the core package must still be be reviewed and streamlined. `ncalc` is actively developed and quite powerful....

@petero-dk Please let's first discuss how to deal with the `ncalc` assembly being unsigned: * Disassemble and reassemble the unsigned Assembly? * Load `ncalc` dynamically? * Use source code directly?

Thank you, @petero-dk, for sharing your thoughts on the necessity of strong-naming the `SmartFormat` NuGet package and its implications, especially in the context of accommodating unsigned packages like `NCalc`. Your...

@petero-dk @Flithor Just [submitted a PR](https://github.com/ncalc/ncalc/pull/129) to publish a signed version besides the unsigned version of `NCalcSync`. Hopefully, it will be accepted.

@petero-dk @Flithor The PR for a signed version of `NCalcSync` has been merged today 👍

> Why don't you add the nuget reference of ZString to your lib and consume it instead of duplicating ZString code and adding it to your lib? This is still...

Agree, NET60 is LTS and should become a target framework. Any reason not mentioning NET80 which is also LTS? Or newer NET80 instead of NET60?