You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
I have been trying to write a routine to reproduce behaviour I have seen occur on several machines.
From what I can tell, it appears to be due to transactional NTFS, but I cannot seem to reproduce it.
The specific behaviour when a file is affected is this:
I can move and rename the file without issues.
If I attempt to delete the file, it appears to delete, but when I refresh the folder, it re-appears. After the attempted deletion, I cannot create a new file with the same name in that folder until after I reboot.
I have tried to create a Visual Studio solution using this library to use transactional NTFS on a specific file.
While the file is opened by my test application, I am unable to delete the file. Windows reports that it is locked by my app.
When the app closes the file, but the transaction has not been closed, I can immediately delete the file with no issues. It does not re-appear after a refresh.
Maybe I am going down the wrong path. I know this isn't the best way to ask this, but I don't know a good avenue to do this.
I greatly appreciate any feedback you can provide.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have been trying to write a routine to reproduce behaviour I have seen occur on several machines.
From what I can tell, it appears to be due to transactional NTFS, but I cannot seem to reproduce it.
The specific behaviour when a file is affected is this:
I have tried to create a Visual Studio solution using this library to use transactional NTFS on a specific file.
While the file is opened by my test application, I am unable to delete the file. Windows reports that it is locked by my app.
When the app closes the file, but the transaction has not been closed, I can immediately delete the file with no issues. It does not re-appear after a refresh.
Note that I have tried posting this to stack overflow, but have not received any responses that reproduce this behaviour.
https://stackoverflow.com/questions/72181020/how-to-simulate-a-specific-style-of-file-locking-where-file-deletes-appear-to-be
I don't do a lot on stack overflow, so I don't have hardly any reputation to offer as a bounty.
Maybe I am going down the wrong path. I know this isn't the best way to ask this, but I don't know a good avenue to do this.
I greatly appreciate any feedback you can provide.
The text was updated successfully, but these errors were encountered: