1.29.1.0

This is a minor update with hotfixes and improvements.

Version [1.29.1.0]

• Fixing bug where log output would not be written to the local log file if remote
  logging was enabled and writing to the remote log file had failed.
• Fixing undesirable behavior in 1.29.0.0 where all attribute change directory notifications
  from file hydration were suppressed. This could even prevent windows explorer from
  showing offline attribute (icon) change without having to refresh. This fix now
  allows one attribute change notification when hydration is complete.
• Addition of common Windows Defender process names to default ExcludedProcessNames,
  instead of having to rely on a custom local configuration to exclude these. Recent
  WD signatures have been aggressively ignoring Offline attribute and sniffing "larger"
  file-types (FBX,MA,SPP) making this almost essential.
• Addition of -a to print command used for file hydration. This can be a significant
  perforce server side optimization allowing lockless reads when db.peeking=2 or 3.
  https://portal.perforce.com/s/article/3839
• Updating to OpenSSL from 3.3.1 to 3.3.3. Now building with no-apps which very
  slightly reduces build time

1.29.0.0

This release contains multiple significant fixes for posted issues. This release also includes a driver version change which may require a PC reboot after installing.

Version [1.29.0.0]

• Fixing virtual file hydration to be excluded from system directory notifications.
  This avoids unecessary FILE_NOTIFY_INFORMATION or DirectoryWatcher events indicating
  a virtual file has been modified, when it's only been hydrated as-expected on read.
  This technique is common across filter drivers. This is only supported for STREAM
  populate method (default). New unit test TestReadDirectoryChanges for verification. (#56)
• Additional unit test variable P4VFS_TEST_SERVER_ROOT for overriding the root directory
  for the test servers. This better facilitates running all tests remotely on a local
  virtual machine with including kernel mode debugging. Includes support for
  RestartPerforceServer script to quick spin-up of existing server on override drive
• Reconfiguring our 32 bit driver allocation pool tags to 4-byte string "Pvs*"
• Fixing bug receiving large messages to/from the P4VFS.Service. This was typically
  encountered when using global "-x " with a file containing many arguments.
  There's a new ReflectPackage message which is now used by SocketModelCommunicationTest
  to stress test a wide range of message sizes (#42)
• Fixing unit tests deterministic random byte generation to more randomly include
  zero as randomly as possible

1.28.3.0

This release includes a minor fix.

Version [1.28.3.0]

• Fixing service initialization error if registry ImagePath value contains quotes
  under key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\P4VFS.Service".
  Including a new unit test to verify handling of user settings paths.
• Updating driver WDK to 10.0.26100

1.28.2.0

This release includes a minor fix.

Version [1.28.2.0]

• Fixing support for specifying a value for P4TICKETS from within a P4CONFIG file,
  and correctly used from working directory of p4vfs.exe, or placeholder file folder
  during service hydration. Service requires P4CONFIG set in system environment or
  system registry.

1.28.1.0

This release fixes a minor intermittent memory leak which has existed prior to the OSS release of P4VFS.

Version [1.28.1.0]

• Fixing possible memory leak during sync operation while accumulating logging
  elements for statistics

1.28.0.0

This release fixes some minor logging bugs and compatibility issues with early versions of Windows Server. It also includes update to latest recommended stable versions of OpenSSL and P4API for security.

Version [1.28.0.0]

• Addition of 'dehydrate' command as synonym for 'resident -v', for changing existing
  files from #have to zero-byte placeholder files. Unit tests included.
• Fixing support for p4vfsflt driver backwards compatibility for Windows Server 2019 and
  earlier, including Windows prior to Windows 10 version 2004. This addressed
  down-level compatibility new zeroed allocation API's such as ExAllocatePool2
• Fixing bug causing some perforce sync errors not to be shown when doing a quite
  single mode sync, such as 'populate', or 'sync -q -m Single'.
• Update to P4API 2024.1 and OpenSSL 3.3.1. UnitTest now uses p4d.exe/p4.exe 2024.1
• Virtual sync details at the start of sync operation now write to StdOut instead of StdErr

1.27.1.0

This release of Microsoft P4VFS now automatically supports Dev Drive for Windows 11. This allows for using P4VFS virtual sync as expected on workspaces residing on high-performance ReFS Dev Drive volumes.

Version [1.27.1.0]

• Now also ignoring specdef tag from P4API results, similar to P4API.NET
• The P4VFS install now configures the driver as allowed by Windows Dev Drive, and the uninstall will remove this exemption.
• Additional native unit tests for windows registry utilities and Dev Drive installation
• Additional Dev Drive unit tests with ReFS virtual hard drive

1.27.0.0

This is the first release use new altsync related features from Perforce server 2023.1 and later. Specifically, the new P4API support for sizes -C option to make placeholder file size to be the same as expected once hydrated. This discrepancy usually occurs with various text filetype's and this correction allows the actual hydrated file size to be determined from a placeholder file's extended attributes. (addresses issue #3)

Version [1.27.0.0]

• New sync -c option to force the placeholder file size to be the expected workspace
  file size, instead of server file size. This requires server 2023.1 or later.
• Updating to P4API 2023.2 and OpenSSL 1.1.1v. UnitTest now uses p4d.exe/p4.exe 2023.1
• P4VFS.External checksum verification fix to handle unexpected whitespace around SHA256
• Driver IRP_MJ_CREATE PostCreate callback fix for properly ignoring reparse on non-P4VFS
  files with FileTag matching our P4VFS_REPARSE_TAG.
• Driver now requires process to be elevated in order to set control parameters (p4vfs ctrl)
• Addition of DepotClient accessor for server protocol level used for testing for server
  features and unicode behavior
• Additional tests for elevated access requirements for internal p4vfsflt control port
  operations
• Fixing stdout display of native unit test assertions and other inner assertions
• Fixing bug where "Text" would appear at the top of the Setup details output.
• Additional tests for both internal ClientSize sync API and p4vfs sync -c

1.26.1.0

The 1.26.1.0 is minor update to fix support for non-ASCII characters in file paths on non-unicode perforce servers.
Primarily fixes issue #15

Version [1.26.1.0]

• Fixing support for file paths including non-ASCII single-byte (CP-1252) encoded characters.
  Additional unit test for handling file paths containing common french accent marks.
• Fixing execution of remote unit tests requiring an installed p4.exe instead of using
  the included P4VFS external binaries

1.24.0.0

First open source release of the Microsoft Virtual File System for Perforce