Two zero byte files crash the Checking function about psfciv HOT 7 CLOSED

Thanks for report, I will investigate this. I'm not sure if I ever tested against zero-byte files, so this certainly can be a bug.

from psfciv.

Hi, sorry for late response.

Finally I've found a time to work on your issue. It appears there are several issues in the code:

1. I'm incorrectly detecting the FCIV mode (native or legacy). I'm examining Size property in XML database which doesn't exist in legacy FCIV and put the script in legacy FCIV processing mode if its value equals to 0 (default for Int64). However, file itself can have zero size. I moved detection to Timestamp property which is more reliable in this case, because it is $null for legacy
2. when legacy mode is ON, I'm using for loop to iterate over entries in DB and access them by index. However, $db.Entries is of type of ISet<T> which doesn't have an indexer.
3. for loop contains several return statements which are meant to be continue.

maybe there are other issues.

from psfciv.

No rush. I'm just happy you are continuing development of this awesome program.

Thanks for stepping through the code and identifying these different legacy mode issues.

I keep checking back every so often on GitHub and PowerShell Gallery to see if there is a new version of PsFCIV to try out.

from psfciv.

Hello, hope you are well. I believe I've fixed your issue. If you wouldn't mind, please check the most recent version of Start-PsFCIV.ps1 file from this repo and confirm if issue is resolved. If it is, I will update the release on PowerShell Gallery.

There is another

from psfciv.

Happy New Year!

Great!! I've tested the updated code against my data set containing zero byte files, and it now works perfectly while checking DB.xml

Thanks again for looking into this.

from psfciv.

I just want to let you know that updated version is published to PowerShell Gallery as v1.1.

from psfciv.

how store the file relative path in db, but not the absolute path

from psfciv.