Walter 2024.3.18.2046

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
dotnet add package Walter --version 2024.3.18.2046
NuGet\Install-Package Walter -Version 2024.3.18.2046
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Walter" Version="2024.3.18.2046" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Walter --version 2024.3.18.2046
#r "nuget: Walter, 2024.3.18.2046"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Walter as a Cake Addin
#addin nuget:?package=Walter&version=2024.3.18.2046

// Install Walter as a Cake Tool
#tool nuget:?package=Walter&version=2024.3.18.2046

WALTER

Introducing the WALTER Framework: Workable Algorithms for Location-aware Transmission, Encryption Response. Designed for modern developers, WALTER is a groundbreaking suite of NuGet packages crafted for excellence in .NET Standard 2.0, 2.1, Core 3.1, and .NET 6, 7, 8, as well as C++ environments. Emphasizing 100% AoT support and reflection-free operations, this framework is the epitome of performance and stability.

Whether you're tackling networking, encryption, or secure communication, WALTER offers unparalleled efficiency and precision in processing, making it an essential tool for developers who prioritize speed and memory management in their applications.

About this Nuget Package

This NuGet package contains helpful extension methods for any .NET project targeting anything from the Web to MAUI, Native Windows, Linux, or Mac. Even though this NuGet package is not intended for direct use, it does come with some handy features. You can download the cmpiled help file as well as see code samples in github

Ahead-Of-Time (AOT) Compilation Compliant

The NuGet package can be used with projects that are trimming and use AoT. However, Newtonsoft Json is not AoT compliant as it uses reflection; therefore, Newtonsoft extension methods are excluded from AoT support.

Json Extensions

We offer helpful extension methods for when you need to process Large JSON files and can't load the whole file in memory as well as exception free processing of json files, strings and streams using the IsValidJson<T>() extension method

The JsonStreamReader<T> class in the Walter namespace is a powerful utility for deserializing JSON data from streams in .NET. This class provides a seamless way to read JSON content instance by instance, handling exceptions gracefully, and is compliant with various .NET versions including .NET Standard 2.0, 2.1, Core 3.1, and .NET 6, 7, 8. It's designed to work efficiently.

Usage

The class is used for reading JSON data from a stream, with error handling mechanisms to capture any exceptions during the deserialization process.

Process a file row by row so you do not have to have the whole file in memory while processing it.

using var stream = File.OpenRead("AppData\\LinkedIn.json");
var sr = new Walter.JsonStreamReader<TCPIPNetwork>(stream,TCPIPNetworkJsonContext.Default.TCPIPNetwork);
int i=0;
var result= new List<TCPIPNetwork>();
await foreach (TCPIPNetwork item in sr.ReadAsync())
{
    i++;
    result.Add(item)
    if(sr.Errors.Count>0)
    {
        _logger.LogError(sr.Errors[^1]
                        ,"File line {line}, failed so entry {i} is skipped as it failed due to {error}"
                        ,sr.Errors[^1].LineNumber,i+1,sr.Errors[^1].Message);
        
    }

}

Process data from a webservice

The sample shows fetching a JSON stream from a web service streaming endpoint and processing the data row by row:

using System.Net.Http;
using System.IO;
using System.Threading.Tasks;

// ... other necessary namespaces

public async Task ProcessJsonDataFromWebServiceAsync()
{
    using var httpClient = new HttpClient();
    try
    {
        var response = await httpClient.GetStreamAsync("https://example.com/api/datastream");
        
        var sr = new Walter.JsonStreamReader<TCPIPNetwork>(response, TCPIPNetworkJsonContext.Default.TCPIPNetwork);
        int i = 0;
        await foreach (TCPIPNetwork item in sr.ReadAsync())
        {
            i++;
            // Process each item
            // ...

            if (sr.Errors.Count > 0)
            {
                _logger.LogError(sr.Errors[i - 1],
                                 "File line {line}, failed so entry {i} is skipped as it failed due to {error}",
                                 sr.Errors[i - 1].LineNumber, i, sr.Errors[i - 1].Message);
            }
        }
    }
    catch (HttpRequestException e)
    {
        _logger.LogError("Error fetching data from web service: {Message}", e.Message);
    }
}

Read a file in one time and process all entries skip those that would fail

using var stream = File.OpenRead("TestData\\LinkedIn.json");
var sr = new Walter.JsonStreamReader<List<TCPIPNetwork>>(stream,TCPIPNetworkListJsonContext.Default.ListTCPIPNetwork);
var list = sr.Read();

foreach (var item in list)
{
 ...
}

String extension methods

This NuGet package includes a range of useful extension methods, enhancing functionality for JSON processing, conversions between hex and bytes, and handling SQL Server varbinary types. For additional examples and comprehensive documentation, you can visit the GitHub repository.

ToSqlBinaryString() integration of Encrypted Data into T-SQL Command

The encryptedBytes.ToSqlBinaryString() method is utilized to convert the byte array (which is the result of the encryption process) into a SQL Server-friendly varbinary format. This format is compatible with T-SQL syntax and is necessary for correctly storing the encrypted data in the database.

The resulting string, prefixed with 0x, represents the hexadecimal representation of the encrypted data. This string is directly embedded into the T-SQL command, allowing the encrypted data to be used in database operations such as INSERT or UPDATE statements. In this way, the encrypted data can be stored securely in the database while maintaining the ability to perform standard SQL operations on it.

var encryptedDataString = encryptedBytes.ToSqlBinaryString();
var tsql = @$"
    DECLARE @EncryptedData VARBINARY(64) = {encryptedDataString};
    ...
    INSERT INTO MyTable (EncryptedColumn) VALUES (@EncryptedData);
";

Secure encryption and decryption

Sample Test Cases for Understanding the Deterministic Encryption

Deterministic encryption is a method where identical plain text values are always encrypted into identical cipher text. This approach is particularly useful in scenarios where you need to:

  • Store Sensitive Data on Third-party Servers: Especially relevant under GDPR compliance when using cloud services where you don't have control over the underlying hardware or database encryption mechanisms.
  • Enable Grouping and Searching: Deterministic encryption allows for the encrypted data to be searchable and groupable, which is essential for performing database operations without decrypting the data, thus maintaining security and privacy.

Benefits and Considerations

  • Data Privacy and Security: Ensures that sensitive data, such as personal information or proprietary corporate data, is stored securely, even in environments not directly controlled by your organization.
  • Searchability and Operational Efficiency: Unlike other forms of encryption, deterministic encryption allows for efficient database operations such as indexing, searching, and grouping on encrypted data.
  • Compliance with Regulations: Meets the requirements of regulations like GDPR, which mandate the protection of personal data, especially when processed or stored on external or cloud-based systems.

When to Use

  • GDPR Compliance in Cloud-Based Storage: Ideal for scenarios requiring GDPR compliance while using cloud-based databases.
  • Maintaining Operational Capabilities: When the ability to search or group data directly in the database is necessary for operational efficiency.

Important Considerations

  • Not a One-Size-Fits-All Solution: Deterministic encryption is a tool among many in the security engineer's toolkit and should be used judiciously. It is not always the preferred method of encryption but can be effective for specific use cases.
  • Secure Key Management: The security of deterministic encryption heavily relies on how the encryption keys are managed. It is crucial to ensure these keys are stored and handled securely, separate from the data they encrypt.

Deterministic encryption provides a balance between operational functionality and data security, making it a valuable option for specific use cases in cloud-based applications and services, particularly where GDPR compliance is a concern.

// Sample to demonstrate GDPR-compliant encryption of sensitive data using deterministic encryption
// for storage in a third-party hosted SQL server.

// Define the company name to be encrypted.
string companyName = "Undefined Corp";

// Create an instance of the symmetric encryption service with a secure password and salt.
// Note: In a production environment, securely manage the password and salt, avoiding hardcoded values.
var encryptionService = new Walter.Cypher.DeterministicEncryption(
    password: "My $ectet Pa$w0rd",
    salt: "123456789+*ç%&/"
);

// Encrypt the company name into a byte array.
byte[] encryptedBytes = encryptionService.Encrypt(companyName.ToBytes());

// Prepare the T-SQL command for data insertion, using the encrypted company name.
var tsql = @$"
DECLARE @UndefinedCorp VARBINARY(64) = {encryptedBytes.ToSqlBinaryString()};
DECLARE @checksum int = CHECKSUM(@UndefinedCorp);

// Check for the existence of the company and insert if not present.
if not exists(select * from [dbo].[Companies] where [CompanyName] = @UndefinedCorp and [cs_CompanyName] = @checksum)
BEGIN
    INSERT [dbo].[Companies] ([CompanyName],[cs_CompanyName],[TrueUpDays],[AutoInvoice],[ApplicableLicenseExcempt])
    Values(@UndefinedCorp, @checksum, -1, 0, 1);
END
";

// Execute the T-SQL command to store the encrypted data.
using var con = new SqlConnection(config.GetConnectionString("Billing"));
using var cmd = con.CreateCommand();
cmd.CommandText = tsql;
cmd.CommandType = System.Data.CommandType.Text;
con.Open();
cmd.ExecuteNonQuery();

Sample Test Cases for Understanding the Symmetric Encryption

We've included sample test cases in our codebase to demonstrate the functionality of the Symmetric Encryption process. These samples are crafted not just to test the code, but also to serve as practical examples for those looking to understand the encryption and decryption mechanisms in depth.

Why Test Cases?
  • Hands-On Learning: By setting breakpoints and stepping through these tests, you can gain a hands-on understanding of how the encryption and decryption process works.
  • Debugging and Inspection: It's an excellent opportunity to inspect the flow of data, observe how the encryption algorithm behaves, and understand how different components interact.
  • Real-World Examples: These tests are more than theoretical scenarios; they represent real-world use cases, helping you relate the functionality to practical applications.
What's in the Sample?
  • Encryption Consistency Test: Encrypt_WithSamePassword_ShouldGenerateDifferentCiphertexts ensures that the encryption process is secure and generates different ciphertexts for the same plaintext.
  • Cross-Instance Compatibility Test: EncryptAndDecrypt_WithDifferentInstances_ShouldBeCompatible confirms that the encrypted data by one instance can be decrypted by another, ensuring consistency across different instances.
How to Use the Sample

Understood, let's adjust the instructions to focus on using the NuGet package directly without the need for cloning a repository. Here's the revised section for your README.md:

markdown Copy code

How to Use the Sample

To effectively use and understand the Symmetric Encryption examples in the 'walter' NuGet package, follow these steps:

  1. Install the 'walter' NuGet Package: Start by adding the 'walter' package to your C# project. This package is essential as it contains the components you'll need for the encryption examples.
  2. Navigate to your Tests: Copy and past the test cases in the project's test project.
  3. Set Breakpoints: Place breakpoints at critical points in the tests.
  4. Debug and Step Through: Run the tests in debug mode and step through the code to observe how the encryption process is executed and validated.

We encourage you to explore these tests to deepen your understanding of symmetric encryption in a .NET environment.

[TestClass]
public class SymmetricEncryptionTests
{
    // This test verifies that the same text encrypted with the same password generates different byte arrays.
    // This is important to ensure that the encryption algorithm uses a unique initialization vector (IV) for each encryption,
    // which enhances security by producing different ciphertexts for the same plaintext.
    [TestMethod]
    public void Encrypt_WithSamePassword_ShouldGenerateDifferentCiphertexts()
    {
        var secretText = "Hello World";
        var encryptionInstance1 = new SymmetricEncryption("TestPassword");
        var encryptionInstance2 = new SymmetricEncryption("TestPassword");

        byte[] encryptedBytes1 = encryptionInstance1.Encrypt(Encoding.UTF8.GetBytes(secretText));
        byte[] encryptedBytes2 = encryptionInstance2.Encrypt(Encoding.UTF8.GetBytes(secretText));

        string ciphertext1 = Encoding.UTF8.GetString(encryptedBytes1);
        string ciphertext2 = Encoding.UTF8.GetString(encryptedBytes2);

        Assert.AreNotEqual(ciphertext1, ciphertext2, "Encrypted bytes should be different for the same input text.");

        string decryptedText1 = Encoding.UTF8.GetString(encryptionInstance1.Decrypt(encryptedBytes1));
        string decryptedText2 = Encoding.UTF8.GetString(encryptionInstance2.Decrypt(encryptedBytes2));

        Assert.AreEqual(decryptedText1, decryptedText2, "Decrypted texts should match the original secret text.");
    }

    // This test ensures that text encrypted by one instance of the SymmetricEncryption class
    // can be decrypted by another instance using the same password. This is crucial for verifying
    // that the encryption and decryption processes are compatible and consistent across different instances.
    [TestMethod]
    public void EncryptAndDecrypt_WithDifferentInstances_ShouldBeCompatible()
    {
        var secretText = "Hello World";
        var encryptionInstanceClient = new SymmetricEncryption("TestPassword");
        var encryptionInstanceServer = new SymmetricEncryption("TestPassword");

        string ciphertext = encryptionInstanceClient.EncryptString(secretText);
        string decryptedText = encryptionInstanceServer.DecryptString(ciphertext);

        Assert.AreEqual(secretText, decryptedText, "Decrypted text should match the original secret text.");
    }
}

Extension methods

There are several extension methods that are usfull like ToBytes() and ToSqlBinaryString() as shown in the bellow code sample.

In the sample bellow we show how you could pre-populat database defaults in a GDPR compliant way where you can use the framweork to generate predefined standard values.

var corp = "Undefined Corp";
var cypher = new Walter.Cypher.SymmetricEncryption(password: "My $ectet Pa$w0rd"
                                             , padding: System.Security.Cryptography.PaddingMode.PKCS7
                                             );

byte[] bytes = cypher.Encrypt(corp.ToBytes());
var tsql = @$"
    declare @UndefinedCorp Varbinary(64) = {bytes.ToSqlBinaryString()};
    declare @checksum int = CHECKSUM(@UndefinedCorp);

    if not exists(select * from  [dbo].[Companies] where [CompanyName] =@UndefinedCorp and [cs_CompanyName]= @checksum)
    BEGIN
        INSERT [dbo].[Companies] ([CompanyName],[cs_CompanyName],[TrueUpDays],[AutoInvoice])
        Values(@UndefinedCorp,@checksum,-1,0);
    END
";
using var con = new SqlConnection(config.GetConnectionString("Billing"));
using var cmd = con.CreateCommand();
cmd.CommandText = tsql;
cmd.CommandType = System.Data.CommandType.Text;
con.Open();
cmd.ExecuteNonQuery();

AoT Exceptions Extension for .NET

The ExceptionsExtension class is a powerful utility for .NET developers, enhancing exception handling with additional diagnostic information. This extension provides methods to extract class names, method names, file names, and approximate line numbers from exceptions especially usefull in AoT.

Features
  • ClassName: Retrieves the class name where the exception originated.
  • MethodName: Obtains the method name that generated the exception.
  • FileName: Gets the filename of the class that generated the exception.
  • CodeLineNumber: Provides the actual or approximate line number where the exception was thrown.
Usage

Here is a examples of how to use the ExceptionsExtension method:

try
{
    _ = File.Open("A:\\doesNotExist.txt", FileMode.Open);
}
catch (Exception e)
{
    //if the binary is AoT compiled the line number is this line
    _logger.LogError(e, "{Class}.{method} (line {line}) failed with a {exception}:{message}",e.ClassName(), e.MethodName(), e.CodeLineNumber(),e.GetType().Name,e.Message);
}

Visit www.asp-waf.com for more information.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 is compatible. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 is compatible. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on Walter:

Package Downloads
Walter.Cypher The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

The cypher package for hashing data in a convenient and secure way as well as symmetric and asymmetric encryption methods.You can find On-line documentation at https://cypherapi.asp-waf.com/ as well as using the sample code found at https://github.com/ASP-WAF/Cypher

Walter.Web.HtmlTools.HtmlMinify

This package allows you to minify HTML generated by MVC projects making the response generally smaller as well as less readable for those that want to copy or work.

Walter.Cypher.Native.Json The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

The cypher package targeting native json and securing data in transit via custome converters.

Walter.Cypher.Newtonsoft.Json The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

The cypher package targeting newtonsoft json and securing data in transit via custome converters.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2024.3.18.2046 21 3/18/2024
2024.3.18.2030 17 3/18/2024
2024.3.18.1707 35 3/18/2024
2024.3.12.1022 146 3/12/2024
2024.3.7.836 197 3/7/2024
2024.3.6.1645 115 3/6/2024
2024.3.3.842 201 3/3/2024
2024.3.1.1143 146 3/1/2024
2024.2.27.1029 141 2/27/2024
2024.2.25.1737 86 2/25/2024
2024.2.19.1557 95 2/21/2024
2024.2.6.759 105 2/6/2024
2024.2.5.1743 87 2/6/2024
2024.2.1.1335 73 2/1/2024
2024.1.22.746 99 1/22/2024
2024.1.21.1514 75 1/21/2024
2024.1.20.1130 72 1/20/2024
2024.1.19.1524 85 1/19/2024
2023.12.5.856 134 12/5/2023
2023.10.12.1926 3,281 10/12/2023
2023.9.14.812 1,432 9/14/2023
2023.8.29.1040 7,820 8/29/2023
2023.8.17.903 1,522 8/17/2023
2023.8.9.1314 1,608 8/9/2023
2023.8.2.750 1,697 8/2/2023
2023.7.12.830 1,718 7/12/2023
2023.7.5.1419 1,798 7/6/2023
2023.6.14.1628 3,309 6/14/2023
2023.5.30.1640 2,208 5/30/2023
2023.5.4.1552 2,278 5/4/2023
2023.4.12.1236 6,219 4/12/2023
2023.3.14.1356 5,016 3/14/2023
2023.3.1.810 2,961 3/1/2023
2023.2.25.1185 935 2/25/2023
2023.2.22.27 5,198 2/22/2023
2023.2.15.1413 3,174 2/15/2023
2023.2.11.1628 3,157 2/11/2023
2023.1.11.534 3,511 1/11/2023
2022.12.14.648 12,049 12/14/2022
2022.11.27.1059 3,881 11/27/2022
2022.11.21.338 3,954 11/21/2022
2022.11.14.1819 4,170 11/14/2022
2022.11.14.1533 733 11/14/2022
2022.11.13.830 371 11/13/2022
2022.10.31.740 7,809 11/1/2022
2022.10.15.652 8,088 10/15/2022
2022.10.1.810 9,966 10/1/2022
2022.9.26.1444 10,659 9/26/2022
2022.9.14.809 9,298 9/14/2022
2022.9.8.1009 17,681 9/8/2022
2022.8.20.1007 9,519 8/20/2022
2022.8.1.1 9,816 7/31/2022
2022.7.15.841 18,380 7/15/2022
2022.7.1.1300 9,946 7/1/2022
2022.6.21.647 9,836 6/21/2022
2022.5.4.1010 35,401 5/4/2022
2022.4.10.828 28,643 4/10/2022
2022.3.26.1117 28,253 3/26/2022
2022.2.11.931 48,967 2/17/2022
2022.2.7.1634 506 2/17/2022
2022.1.15.1312 20,464 1/17/2022
2022.1.10.537 19,426 1/10/2022
2022.1.7.1357 9,307 1/8/2022
2021.12.28.1452 10,638 12/28/2021
2021.12.15.911 9,958 12/16/2021
2021.11.19.850 36,090 11/19/2021
2021.11.11.1334 29,498 11/16/2021
2021.11.8.2109 8,561 11/9/2021
2021.11.8.1612 53,022 11/8/2021
2021.10.13.1459 9,536 10/18/2021
2021.10.11.1400 425 10/11/2021
2021.10.9.1133 622 10/10/2021
2021.9.26.1913 62,352 9/26/2021
2021.9.17.1702 14,628 9/18/2021
2021.8.30.1319 91,539 8/30/2021
2021.8.14.1600 50,731 8/16/2021
2021.8.14.829 5,484 8/14/2021
2021.8.8.1612 17,605 8/8/2021
2021.8.8.1138 587 8/8/2021
2021.7.22.1033 60,557 7/23/2021
2021.7.15.1547 9,475 7/15/2021
2021.7.12.734 9,410 7/13/2021
2021.6.26.1753 35,378 6/27/2021
2021.6.23.734 18,308 6/24/2021
2021.6.19.803 9,973 6/20/2021
2021.6.11.1600 35,228 6/13/2021
2021.6.9.1120 9,604 6/9/2021
2021.6.7.1407 2,642 6/7/2021
2021.5.31.1533 17,845 5/31/2021
2021.5.28.1451 9,655 5/31/2021
2021.5.25.1732 8,537 5/25/2021
2021.5.12.929 26,582 5/12/2021
2021.5.12.914 575 5/12/2021
2021.5.12.637 7,066 5/12/2021
2021.5.5.1901 31,166 5/6/2021
2021.5.2.1617 9,227 5/4/2021
2021.4.28.1503 17,830 4/28/2021
2021.4.5.1653 59,831 4/5/2021
2021.4.2.1918 429 4/2/2021
2021.4.1.913 9,419 4/1/2021
2021.3.31.1630 9,350 4/1/2021
2021.3.17.606 9,818 3/18/2021
2021.3.3.1259 665 3/3/2021
2021.3.3.833 638 3/3/2021
2021.3.1.1205 23,507 3/2/2021
2021.3.1.1 16,263 2/27/2021
2021.2.21.3 15,643 2/21/2021
2021.2.19.3 8,904 2/20/2021
2021.2.19.2 8,417 2/19/2021
2021.2.16.1 22,762 2/16/2021
2021.2.15.1 16,382 2/14/2021
2021.2.10.1 36,255 2/10/2021
2021.2.7.1 22,975 2/6/2021
2020.12.27.1 16,105 12/27/2020
2020.12.26.2 23,584 12/27/2020
2020.12.24.2 698 12/26/2020
2020.12.24.1 673 12/24/2020
2020.12.18.1 8,770 12/19/2020
2020.12.15.1 15,716 12/15/2020
2020.12.14.5 11,818 12/14/2020
2020.12.14.4 8,113 12/14/2020
2020.12.14.3 7,920 12/14/2020
2020.11.27.1 64,822 11/27/2020
2020.11.25.1 12,622 11/25/2020
2020.11.23.1 673 11/25/2020
2020.11.22.2 8,445 11/23/2020
2020.11.20.1 7,719 11/21/2020
2020.11.19.3 7,857 11/19/2020
2020.11.11.1 62,655 11/11/2020
2020.10.9.5 122,899 10/9/2020
2020.10.5.1 67,629 10/5/2020
2020.10.4.1 725 10/4/2020
2020.10.1.1 18,082 10/1/2020
2020.9.29.9 12,395 9/29/2020
2020.9.24.2 22,692 9/24/2020
2020.9.11.1 47,627 9/11/2020
2020.9.11 576 9/11/2020
2020.9.8 16,866 9/8/2020
2020.9.6.4 5,154 9/6/2020
2020.9.6.3 719 9/6/2020
2020.9.6.2 2,041 9/6/2020
2020.9.3.1 14,401 9/3/2020

6 March 2024
- Bring native support for [1..] and [..^1] range and index operation to .net standard 2.0 projects
- Brings support for string Replace(this string original, string newValue, StringComparison comparisonType) to .net standard 2.0 projects



1 March 2024
- Add NistClock, extension methods, new methods for Guard class

19 February 2024
- Add Documentation API

3 February 2024
- Enable Logging in Walter Framework using the AddLoggingForWalter extension on the IServiceProvider interface

18 January 2024
- Update package to include other frameworks
- Add new License framework
- Add Cypher, DateTime mocking and other helper methods
- Add and update extension methods to be AOT compatible
- Make nuget package and enable trimming for consuming applications
- see on-line help at https://walter.vesnx.com/

14 November 2023
- Add support for .net 8