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.

Sign up for GitHub

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

Jump to bottom

Update package to .NET 8 (from EOL'd 6) #56

Merged
merged 1 commit into from
Dec 2, 2024
Merged

Update package to .NET 8 (from EOL'd 6) #56

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Directory.Build.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion lib/CopyOnWrite.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down
11 changes: 0 additions & 11 deletions lib/MaxCloneFileLinksExceededException.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@

using System;
using System.IO;
using System.Runtime.Serialization;

namespace Microsoft.CopyOnWrite;

Expand Down Expand Up @@ -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)
{
}
}