From 25c1c917bb06ab90b808e9b7fd61859cd27ae376 Mon Sep 17 00:00:00 2001
From: Erik Mavrinac <erikmav@microsoft.com>
Date: Mon, 2 Dec 2024 10:36:26 -0800
Subject: [PATCH] Update to .NET 8 (from EOL

---
 Directory.Build.props                     |  4 ++--
 README.md                                 |  1 +
 lib/CopyOnWrite.csproj                    |  2 +-
 lib/MaxCloneFileLinksExceededException.cs | 11 -----------
 4 files changed, 4 insertions(+), 14 deletions(-)

diff --git a/Directory.Build.props b/Directory.Build.props
index 8a6b862..1fd2481 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -26,12 +26,12 @@
   <PropertyGroup>
 
     <!-- DOCSYNC: When changing version number update README.md -->
-    <Version>0.4.2</Version>
+    <Version>0.5.0</Version>
     <AssemblyVersion>0.9.9999.0</AssemblyVersion>
 
     <Company>Microsoft</Company>
     <Copyright>Copyright (c) Microsoft Corporation</Copyright>
-    <Description>.NET library that encapsulates OS and filesystem differences in the ability to create Copy-on-Write file links.</Description>
+    <Description>.NET library that implements Copy-on-Write file links for Windows Dev Drive and ReFS.</Description>
     <Product>Microsoft.CopyOnWrite</Product>
 
   </PropertyGroup>
diff --git a/README.md b/README.md
index 4216163..4e6d27f 100644
--- a/README.md
+++ b/README.md
@@ -45,6 +45,7 @@ File clones on Windows do not actually allocate space on-drive for the clone. Th
 
 [![NuGet version (CopyOnWrite)](https://img.shields.io/nuget/v/CopyOnWrite?style=plastic)](https://www.nuget.org/packages/CopyOnWrite)
 
+* 0.5.0 December 2024: Move package framework support from .NET 6 to .NET 8 after 6 reached end-of-life.
 * 0.4.2 November 2024: Loosened error handling getting volume information, any volume resulting in an error is ignored. This aids continued failures finding new unique error types based on al lthe various disk subsystems and drivers out there.
 * 0.4.1 October 2024: Add ERROR_DEV_NOT_EXIST handling on volume enumeration
 * 0.4.0 October 2024: Remove async versions of `CloneFile` as the implementation did not use overlapped I/O anyway. CoW support is releasing in the Server 2025 and Win11 24H2 wave, built into the `CopyFile` API suite and on by default for Dev Drive and ReFS, so overlapped I/O in this library will never be implemented. Resolves https://github.com/microsoft/CopyOnWrite/issues/50
diff --git a/lib/CopyOnWrite.csproj b/lib/CopyOnWrite.csproj
index 1e03267..5b0f0e7 100644
--- a/lib/CopyOnWrite.csproj
+++ b/lib/CopyOnWrite.csproj
@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <RootNamespace>Microsoft.CopyOnWrite</RootNamespace>
-    <TargetFrameworks>netstandard2.0;net6.0</TargetFrameworks>
+    <TargetFrameworks>netstandard2.0;net8.0</TargetFrameworks>
 
     <DistribDir>$(DistribRoot)Package\</DistribDir>
 
diff --git a/lib/MaxCloneFileLinksExceededException.cs b/lib/MaxCloneFileLinksExceededException.cs
index ad20891..fa3ba21 100644
--- a/lib/MaxCloneFileLinksExceededException.cs
+++ b/lib/MaxCloneFileLinksExceededException.cs
@@ -3,7 +3,6 @@
 
 using System;
 using System.IO;
-using System.Runtime.Serialization;
 
 namespace Microsoft.CopyOnWrite;
 
@@ -40,14 +39,4 @@ public MaxCloneFileLinksExceededException(string message, Exception innerExcepti
         : base(message, innerException)
     {
     }
-
-    /// <summary>
-    /// Serialization constructor.
-    /// </summary>
-    /// <param name="info">The serialization info.</param>
-    /// <param name="context">The streaming context.</param>
-    private MaxCloneFileLinksExceededException(SerializationInfo info, StreamingContext context)
-        : base(info, context)
-    {
-    }
 }