2025.1 release

2025.1 release

Author: shraddhaborate

BUILD.md

@@ -2,12 +2,14 @@
 
 These are Build instructions for P4API.net and its required DLL and various test utilities
 
-## The .NET Core (6.0) cross-platform port
+## The .NET Core (8.0) cross-platform port
 
 With the 2021.2 release, `P4API.NET` has been extended to support .NET CORE and to be cross-platform on three Target OS's (Windows, Linux, OSX)
 
 With the 2024.2 release, 'P4API.NET' has been extended to support Linux and Mac ARM64 architecture systems.
 
+With the 2025.1 release, 'P4API.NET' has been extended to support .NET 8.0 and to be cross-platform on three Target OS's (Windows, Linux, OSX) and has dropped support for .NET 6.0.
+
 P4API.NET consists of a DLL written in C++ which contains the Perforce C++ API, which is wrapped by a layer of C# code which exports the .NET interface.
 
 Within this directory are several subprojects.  p4bridge, p4bridge-unit-test, p4bridgeStressTest, p4api.net and p4api.net-unit-test
@@ -17,15 +19,15 @@ Within this directory are several subprojects.  p4bridge, p4bridge-unit-test, p4
 ### p4apicore.net.sln
 
 [p4apicore.net.sln](p4apicore.net.sln) - This solution includes projects [p4api.net.csproj](./p4api.net/p4api.net.csproj)  and [p4api.net-unit-test.csproj](./p4api.net-unit-test/p4api.net-unit-test.csproj). 
-Both of the projects target frameworks .NET Framework 4.6.2, .Net Core 6.0 and .NET Standard 2.0.
+Both of the projects target frameworks .NET Framework 4.6.2, .Net Core 8.0 and .NET Standard 2.0.
 > It only includes the C# portions of the project.
 > It can be built using the `dotnet build p4apicore.net.sln` command.
 This solution can be opened by the "dotnet" executable on any supported platform, or by VS2019+ on windows only.
 This is the primary solution to be used for building and/or debugging P4API.NET and its unit tests.
 
 ### Sample Applications
 
-Sample Console Applications for .NET 6.0 are provided here: 
+Sample Console Applications for .NET 8.0 are provided here: 
 [consoleApps/ControlCTest.sln](consoleApps/ControlCTest.sln) and [consoleApps/P4DotNetConsole.sln](consoleApps/P4DotNetConsole.sln)
 
 Sample Applications for .NET framework are provided here:
@@ -90,14 +92,14 @@ The source, build and configuration instructions for these tests is in the *p4br
 
 **IMPORTANT!** - The C++ bridge must have already been built before building P4API.NET.
 
-Make sure you have an updated .NET 6.0 SDK (or better) installed for your platform.
+Make sure you have an updated .NET 8.0 SDK (or better) installed for your platform.
 download from here: [Microsoft .NET Downloads](https://dotnet.microsoft.com/download)
 
 in the p4api.net root folder run
 `dotnet build p4apicore.net.sln`
 
- This will create The .NET DLL in `p4api.net\bin\Debug\net60\p4api.net.dll`, `p4api.net\bin\Debug\net462\p4api.net.dll`, `p4api.net\bin\Debug\netstandard2.0\p4api.net.dll`
- And the Unit test in `\p4api.net-unit-test\bin\Debug\net60\p4api.net-unit-test.dll`, `\p4api.net-unit-test\bin\Debug\net462\p4api.net-unit-test.dll`, `\p4api.net-unit-test\bin\Debug\netstandard2.0\p4api.net-unit-test.dll`
+ This will create The .NET DLL in `p4api.net\bin\Debug\net80\p4api.net.dll`, `p4api.net\bin\Debug\net462\p4api.net.dll`, `p4api.net\bin\Debug\netstandard2.0\p4api.net.dll`
+ And the Unit test in `\p4api.net-unit-test\bin\Debug\net80\p4api.net-unit-test.dll`, `\p4api.net-unit-test\bin\Debug\net462\p4api.net-unit-test.dll`, `\p4api.net-unit-test\bin\Debug\netstandard2.0\p4api.net-unit-test.dll`
  It will also copy the p4bridge.dll from the appropriate place in the ../p4bridge output into the default output directory.
 
  On Windows, you can specify a specific Configuration and Platform with parameters:
@@ -115,10 +117,10 @@ into proper runtime locations.
 `dotnet test p4apicore.net.sln`
 
 > Filter on the dotnet framework to run upon
->> `dotnet test p4apicore.net.sln -f net60`
+>> `dotnet test p4apicore.net.sln -f net80`
 >
 > Filter on the specific test to run
->> `dotnet test p4apicore.net.sln -f net60 --filter TestName`
+>> `dotnet test p4apicore.net.sln -f net80 --filter TestName`
 
 
 * **Visual Studio 2019** can be used to debug the .NET unit tests if you are running in Windows.
@@ -134,7 +136,7 @@ Unfortunately, you cannot debug through the C++ code using Rider.
 2. Build the four varieties of p4bridge first
 3. `dotnet pack p4apicore.net.sln`
 
-This will create an Assembly DLL in *.\bin\p4api.net\bin\Debug\net6.0\p4api.net.dll*
+This will create an Assembly DLL in *.\bin\p4api.net\bin\Debug\net8.0\p4api.net.dll*
 and a nuget package in:
 *p4api.net\bin\Debug\p4api.net.VERSION.nupkg*
 

LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2024, Perforce Software, Inc. All rights reserved.
+Copyright (c) 2025, Perforce Software, Inc. All rights reserved.
 
 Redistribution and use in source and binary forms, with or without 
 modification, are permitted provided that the following conditions are met:
@@ -40,7 +40,7 @@ this program.
 
 P4/P4API License
 -----------------------
-Copyright (c) 1995-2024, Perforce Software, Inc.
+Copyright (c) 1995-2025, Perforce Software, Inc.
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without

RELEASENOTES.txt

@@ -1,7 +1,7 @@
                            Release Notes for
-                P4API.NET, the Helix P4API for .NET
+                P4API.NET, the P4 API for .NET
 
-                          Version 2024.2
+                          Version 2025.1
 
 Introduction
 
@@ -45,7 +45,7 @@ Building P4API.NET from Source
         P4API.NET supports SSL connections, and requires linking with SSL 
         libraries.
 
-        Executables linked against the P4API libraries must also be linked
+        Executables linked against the P4 C/C++ API libraries must also be linked
         against real OpenSSL libraries: The latest 3.0.x patch is recommended.
         Use the OpenSSL libraries as mentioned in BUILD.md.
 
@@ -60,22 +60,20 @@ Compatibility Statements
 
         Server Compatibility
 
-          You can use this release of P4API.NET with any release of the
-          Perforce server at or later than 2018.1, but to ensure maximum
-          compatibility, it is recommended that you use it with the
-          corresponding Perforce server release
+          This release of P4API.NET supports the P4 Server 2025.1.
+          Older releases might work but are not supported.
 
         API Compatibility
 
-          This release of P4API.NET requires the 2024.2 Helix Core API
-          (2024.2/2675662) for C/C++ (P4API), built with Visual Studio 2019 or 
+          This release of P4API.NET requires the 2025.1 P4 C/C++ API
+          (2025.1/2761706), built with Visual Studio 2019 or 
           later.
 
         C#/.NET Compatibility
 
           This release of P4API.NET, when built from source using 
           p4apicore.net.sln, is compatible with '.NET Framework 4.6.2',
-          '.NET 6.0' and '.NET Standard 2.0'. Other .Net Framework, .NET Core
+          '.NET 8.0' and '.NET Standard 2.0'. Other .Net Framework, .NET Core
           and .NET Standard versions might work, but are not supported.
 
         Platform Compatibility
@@ -103,23 +101,67 @@ Compatibility Statements
         Compatibility with Previous Releases
 
           Unless otherwise stated below, this release of P4API.NET is compatible
-          with previous releases from Perforce Software.
+          with previous releases from P4 Software.
 
----------------------------------------------------------------------------
-Important End-of-Life Notice
+--------------------------------------------------------------------------
+
+Important Product Rebrand Notice
 
-    This major release of P4API.NET would be the last to support '.Net 6.0'.
-    Next major release will add support for '.Net 8.0'.  
-    This is part of our commitment to focus on supported technology platforms.
+        Helix Core is now P4
+        Perforce has a new look and logo that reflects our place in DevOps
+        workflows. As part of these changes, Helix Core is now P4. Name updates
+        and new icons to align with the P4 branding will be rolled out soon.
+        To learn more, see:
+         https://www.perforce.com/blog/vcs/introducing-the-p4-platform
 
 --------------------------------------------------------------------------
 
 Key to symbols used in change notes below.
 
           * -- requires new P4API.NET
-         ** -- requires P4API.NET built with new P4API
+         ** -- requires P4API.NET built with new P4 C/C++ API
         *** -- requires new p4d server program
 
+--------------------------------------------------------------------------
+New functionality in 2025.1 (2025.1/2773624) (2025/06/03)
+
+        #2762830,2763155 (Job #125774) * ** ***
+            Updated P4API.NET to support 2025.1 release of P4 C/C++ API.
+
+        #2754421 (Job #123673) * ** ***
+            Added support for .NET SDK 8.0.
+
+        #2765712,2766915 (Job #124086) * ** ***
+            Added support for sparse stream creation and converting sparse 
+            stream into development/release stream.
+
+        #2749356,2752384 (Job #125614) * ** ***
+            Added support for --sync-time option with -k for p4 sync.
+            The --sync-time specifies the file modification time to 
+            be set when updating the server metadata with the -k flag.
+
+        #2760384 (Job #125905) * ** ***
+            Added support for support -M and --parallel in p4 reconcile.
+            The -M flag allows the missing and added files to be compared and
+            converted to pairs of move/delete and move/add operations if they
+            are similar enough.
+
+        #2762361 (Job #125907) * ** ***
+            Added support for -M and --parallel flag for p4 move.
+            The -M flag matches already opened files for add and delete in the
+            default or specified changelist and reopens them as a move.
+
+--------------------------------------------------------------------------
+Bugs fixed in 2025.1 (2025.1/2773624) (2025/06/03)
+
+        #2750543 (Job #125040) *
+            Handled exception for GetFileHistory where start revision
+            and end revision was exceeding limit for Int16.
+
+        #2766575 (Job #124034) *
+            Corrected documentation for usage of GetFileContents
+            and GetFileContentsEx methods.
+
 --------------------------------------------------------------------------
 New functionality in 2024.2 (2024.2/2693570) (2024/12/10)
 

consoleApps/ControlCTest/ControlCTest.csproj

@@ -1,8 +1,8 @@
-<Project Sdk="Microsoft.NET.Sdk">
+<Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
     <OutputType>Exe</OutputType>
-    <TargetFramework>net5.0</TargetFramework>
+    <TargetFramework>net8.0</TargetFramework>
   </PropertyGroup>
 
   <ItemGroup>

consoleApps/P4DotNetConsole/P4DotNetConsole.csproj

@@ -1,8 +1,8 @@
-<Project Sdk="Microsoft.NET.Sdk">
+<Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
     <OutputType>Exe</OutputType>
-    <TargetFramework>net6.0</TargetFramework>
+    <TargetFramework>net8.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
   </PropertyGroup>