Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next dev 0.8.5 #36

Merged
merged 41 commits into from
Dec 26, 2023
Merged

Next dev 0.8.5 #36

merged 41 commits into from
Dec 26, 2023

Conversation

dmitry-merzlyakov
Copy link
Owner

0.8.5 (2023-12-28)

Release Information

  • Support for multi-target deployments
  • Migrating to LTS .Net versions
  • Created .Net Ledger Tools management console
  • Bug fixing

Features

  • Default solution targets are changed to current LTS versions (.Net Framework 4.8, .Net 6.0, .Net 8)
  • Public packages (MSI and ZIP) are distributed with pre-built binaries for LTS targets
  • Public NuGet package includes Standard 2.0, .Net 6.0 and .Net 8 targets
  • Development build script get-nledger-up.ps1 is changed to support custom targets. Developers can build and test binaries for any supported .Net versions.
  • Development build script get-nledger-up.ps1 is changed to reflect local environment limitations. Non-available targets are silently skipped.
  • Added a single management console .Net Ledger Tools that incorporates commands for installation, configuration, testing, Python management and running interactive demo

Known Issues

  • Listed in ProductInfo.xml
  • NLedger Python module requires PythonNet module version 2.5.2 or 3.0.0-pre. Adding support for PythonNet 3.0.3 is addressed by further development.

Bug Fixing

Breaking Changes

  • .Net Ledger Tools management console replaces interactive PowerShell scripts for installing, testing, Python management and running Live Demo.

dmitry-merzlyakov and others added 30 commits March 14, 2022 18:15
…0; all tests passed (including .Net/Python integration). One test was corrected to reflect changes in net6 core libraries (compatibility with .Net Framework and core 3.1 is kept).
…AndFilesBecauseOfNoFile was potentially affected by a physical default ledger file on the host machine
…he original state since typos were made for purpose).
…he function of adding two Amounts with commodities: when the left operand had lower precision than the right operand, the precision of the result was not changed to a higher value. In some cases, this caused problems with zero balance detection—zero precision in the balance amount required calculating the real zero without rounding, which ultimately resulted in a false positive balance check.
… unit tests passed; dotnet cli and VS builds work well.
@dmitry-merzlyakov dmitry-merzlyakov merged commit 45c6464 into next-dev Dec 26, 2023
@dmitry-merzlyakov dmitry-merzlyakov deleted the next-dev-0.8.5 branch December 26, 2023 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants