Releases: badcel/WCharT.Net
Releases · badcel/WCharT.Net
0.1.3
This is a minor update which drops dotnet 6.0 support and adds dotnet 9.0 support.
What's Changed
- Bump MSTest.TestAdapter from 3.4.3 to 3.5.0 in /src by @dependabot in #12
- Bump MSTest.TestFramework from 3.4.3 to 3.5.0 in /src by @dependabot in #13
- Bump MSTest.TestAdapter from 3.5.0 to 3.5.1 in /src by @dependabot in #14
- Bump MSTest.TestFramework from 3.5.0 to 3.5.1 in /src by @dependabot in #15
- Bump MSTest.TestAdapter from 3.5.1 to 3.5.2 in /src by @dependabot in #16
- Bump MSTest.TestFramework from 3.5.1 to 3.5.2 in /src by @dependabot in #17
- Bump Microsoft.NET.Test.Sdk from 17.10.0 to 17.11.0 in /src by @dependabot in #18
- Update target frameworks by @badcel in #32
- WCharT.Net.Tests: Update dependencies by @badcel in #33
Full Changelog: 0.1.2...0.1.3
Contributors
badcel and dependabot
Assets 2
0.1.2
This release primarily fixes a bug in case WCharTString was used as a buffer. The given buffer size was implicitly increased by one character, so the native code would be allowed to add a null termination sign after the requested size of the buffer. This is not expected from a public API. If a buffer for a certain amount of characters is created, the caller should know if there is memory for a null termination sign needed or not. It should not be implicitly added for every buffer request.
What's Changed
- Move platform specific code into a platform class by @badcel in #8
- Simplify compile time constants by @badcel in #9
- Add doc comments by @badcel in #10
- Bug: No automatic null termination in case of buffer scenario by @badcel in #11
Full Changelog: 0.1.1...0.1.2
Contributors
badcel
Assets 2
0.1.1
This is a bugfix release of WCharT.Net.
Fixed issues:
- Nuget: If the package was used with a windows operating system the
WCharT.Netbinary was not found during runtime because the package used an invalid runtime identifier for windows. - Nuget: Use updated package project url
Full Changelog: 0.1.0...0.1.1