update: added messagepack-csharp serialization support

- Added serialization support to bound structs

Author: mrdav30

.assets/scripts/set-version-and-build.ps1

@@ -14,4 +14,35 @@ Set-Location $solutionDir
 Ensure-GitVersion-Environment
 
 # Build the project with the version information applied
-Build-Project -Configuration $BuildType
+Build-Project -Configuration $BuildType
+
+# Output directory
+$releaseDir = Join-Path $solutionDir "src\$solutionDir\bin\Release"
+
+# Ensure release directory exists
+if (Test-Path $releaseDir) {
+    Get-ChildItem -Path $releaseDir -Directory | ForEach-Object {
+        $targetDir = $_.FullName
+        $frameworkName = $_.Name
+
+        # Construct final archive name
+        $zipFileName = "${solutionDir}-v${GitVersion_FullSemVer}-${frameworkName}-release.zip"
+        $zipPath = Join-Path $releaseDir $zipFileName
+
+        Write-Host "Creating archive: $zipPath"
+
+        if (Test-Path $zipPath) {
+            Remove-Item $zipPath -Force
+        }
+
+        Compress-Archive -Path "$targetDir\*" -DestinationPath $zipPath -Force
+
+        if (Test-Path $zipPath) {
+            Write-Host "✔ Archive created for $frameworkName"
+        } else {
+            Write-Warning "⚠ Failed to create archive for $frameworkName"
+        }
+    }
+} else {
+    Write-Warning "⚠ Release directory not found: $releaseDir"
+}

.assets/scripts/utilities.ps1

@@ -1,9 +1,12 @@
 function Get-SolutionDirectory {
-    param ([string]$StartPath = $(Get-Location))
+    param (
+		[string]$StartPath = $(Get-Location),
+		[string]$SolutionPath = "FixedMathSharp.sln"
+	)
 
     $currentPath = $StartPath
     while ($true) {
-        if (Test-Path (Join-Path $currentPath "FixedMathSharp.sln")) {
+        if (Test-Path (Join-Path $currentPath $SolutionPath)) {
             return $currentPath
         }
         $parent = [System.IO.Directory]::GetParent($currentPath)

CONTRIBUTING.md

@@ -0,0 +1,92 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
+   build.
+2. Update the README.md with details of changes to the interface, this includes new environment 
+   variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at `[email protected]`. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

README.md

@@ -20,6 +20,7 @@ Ideal for simulations, games, and physics engines requiring reliable arithmetic
 - **Bounding Shapes:** Includes `IBound` structs `BoundingBox`, `BoundingSphere`, and `BoundingArea` for lightweight spatial calculations.
 - **Advanced Math Functions:** Includes trigonometry and common math utilities.
 - **Framework Agnostic:** Works with **.NET, Unity, and other game engines**.
+- **Full Serialization Support:** Out-of-the-box round-trip serialization via BinaryFormatter (for .NET Framework 4.8+), System.Text.Json (for .NET 8+), and MessagePack across all serializable structs.
 
 ---
 
@@ -115,15 +116,11 @@ Console.WriteLine(sinValue); // Output: ~0.707
 - **`IBound` Interface:** Standard interface for bounding shapes `BoundingBox`, `BoundingArea`, and `BoundingSphere`, each offering intersection, containment, and projection logic.
 - **`FixedMath` Static Class:** Provides common math and trigonometric functions using fixed-point math.
 - **`Fixed4x4` and `Fixed3x3`:** Support matrix operations for transformations.
-- **`FixedMathSharp.Editor`:** Extensions for seamless integration with Unity, including property drawers and type conversions.
 
 ### Fixed64 Struct
 
-**Fixed64** is the core data type representing fixed-point numbers. It 
-provides various mathematical operations, including addition,
-subtraction, multiplication, division, and more. The struct guarantees
-deterministic behavior by using integer-based arithmetic with a
-configurable `SHIFT_AMOUNT`.
+**Fixed64** is the core data type representing fixed-point numbers. It provides various mathematical operations, including addition, subtraction, multiplication, division, and more. 
+The struct guarantees deterministic behavior by using integer-based arithmetic with a configurable `SHIFT_AMOUNT`.
 
 ---
 
@@ -138,13 +135,12 @@ FixedMathSharp is optimized for high-performance deterministic calculations:
 
 ## 🧪 Testing and Validation
 
-Unit tests are used extensively to validate the correctness of mathematical 
-operations. Special **fuzzy comparisons** are employed where small precision 
-discrepancies might occur, mimicking floating-point behavior.
+Unit tests are used extensively to validate the correctness of mathematical operations. 
+Special **fuzzy comparisons** are employed where small precision discrepancies might occur, mimicking floating-point behavior.
 
 To run the tests:
 ```bash
-dotnet test --configuration Release
+dotnet test --configuration debug
 ```
 
 ---
@@ -158,10 +154,13 @@ dotnet test --configuration Release
 
 ---
 
+## 🤝 Contributing
+
+We welcome contributions! Please see our [CONTRIBUTING](https://github.com/mrdav30/FixedMathSharp/blob/main/CONTRIBUTING.md) guide for details on how to propose changes, report issues, and interact with the community.
+
 ## 📄 License
 
-This project is licensed under the MIT License - see the `LICENSE` file
-for details.
+This project is licensed under the MIT License - see the [LICENSE](https://github.com/mrdav30/FixedMathSharp/blob/main/LICENSE.md) for details.
 
 ---
 

src/FixedMathSharp/Bounds/BoundingArea.cs

@@ -1,4 +1,5 @@
-using System;
+using MessagePack;
+using System;
 using System.Runtime.CompilerServices;
 
 namespace FixedMathSharp
@@ -17,18 +18,21 @@ namespace FixedMathSharp
     /// </remarks>
 
     [Serializable]
+    [MessagePackObject]
     public struct BoundingArea : IBound, IEquatable<BoundingArea>
     {
         #region Fields
 
         /// <summary>
         /// One of the corner points of the bounding area.
         /// </summary>
+        [Key(0)]
         public Vector3d Corner1;
 
         /// <summary>
         /// The opposite corner point of the bounding area.
         /// </summary>
+        [Key(1)]
         public Vector3d Corner2;
 
         #endregion
@@ -64,48 +68,59 @@ public BoundingArea(Vector3d corner1, Vector3d corner2)
         /// <summary>
         /// The minimum corner of the bounding box.
         /// </summary>
+        [IgnoreMember]
         public Vector3d Min
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
-            get => new Vector3d(MinX, MinY, MinZ);
+            get => new(MinX, MinY, MinZ);
         }
 
         /// <summary>
         /// The maximum corner of the bounding box.
         /// </summary>
+        [IgnoreMember]
         public Vector3d Max
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
-            get => new Vector3d(MaxX, MaxY, MaxZ);
+            get => new(MaxX, MaxY, MaxZ);
         }
 
+        [IgnoreMember]
         public Fixed64 MinX
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
             get => Corner1.x < Corner2.x ? Corner1.x : Corner2.x;
         }
+
+        [IgnoreMember]
         public Fixed64 MaxX
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
             get => Corner1.x > Corner2.x ? Corner1.x : Corner2.x;
         }
 
+        [IgnoreMember]
         public Fixed64 MinY
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
             get => Corner1.y < Corner2.y ? Corner1.y : Corner2.y;
         }
+
+        [IgnoreMember]
         public Fixed64 MaxY
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
             get => Corner1.y > Corner2.y ? Corner1.y : Corner2.y;
         }
 
+        [IgnoreMember]
         public Fixed64 MinZ
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
             get => Corner1.z < Corner2.z ? Corner1.z : Corner2.z;
         }
+
+        [IgnoreMember]
         public Fixed64 MaxZ
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
@@ -115,6 +130,7 @@ public Fixed64 MaxZ
         /// <summary>
         /// Calculates the width (X-axis) of the bounding area.
         /// </summary>
+        [IgnoreMember]
         public Fixed64 Width
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
@@ -124,6 +140,7 @@ public Fixed64 Width
         /// <summary>
         /// Calculates the height (Y-axis) of the bounding area.
         /// </summary>
+        [IgnoreMember]
         public Fixed64 Height
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
@@ -133,6 +150,7 @@ public Fixed64 Height
         /// <summary>
         /// Calculates the depth (Z-axis) of the bounding area.
         /// </summary>
+        [IgnoreMember]
         public Fixed64 Depth
         {
             [MethodImpl(MethodImplOptions.AggressiveInlining)]
@@ -203,7 +221,7 @@ public Vector3d ProjectPoint(Vector3d point)
         #region Equality and HashCode Overrides
 
         [MethodImpl(MethodImplOptions.AggressiveInlining)]
-        public override bool Equals(object obj) => obj is BoundingArea other && Equals(other);
+        public override bool Equals(object? obj) => obj is BoundingArea other && Equals(other);
 
         [MethodImpl(MethodImplOptions.AggressiveInlining)]
         public bool Equals(BoundingArea other) => Corner1.Equals(other.Corner1) && Corner2.Equals(other.Corner2);