SharpSFV - A Spiritual Sucessor to QuickSFV

[Razer-785]

Hello i am sorry if this is a stupid question but how can i make the checksum without the folder path. i am trying to implement this into a installer/setup but i don't want to have to edit the checksum file each time to remove the file path.

the file named "checksums-original.txt" is what i get if i do it normally copy the folder path and press ctl+v in the software.

and the file named "checksums-fixed.txt" is what i need, i already tested it and it works.

but if you can help me with this that would be great, also im kinda new so im sorry if this is kinda weird or does not make sense.

PS. Awesome program works really well

[L33THAK0R]

Originally Posted by Razer-785

Hello i am sorry if this is a stupid question but how can i make the checksum without the folder path. i am trying to implement this into a installer/setup but i don't want to have to edit the checksum file each time to remove the file path.

the file named "checksums-original.txt" is what i get if i do it normally copy the folder path and press ctl+v in the software.

and the file named "checksums-fixed.txt" is what i need, i already tested it and it works.

but if you can help me with this that would be great, also im kinda new so im sorry if this is kinda weird or does not make sense.

PS. Awesome program works really well

In the options tool-bar, you've enabled the "Always Save Absolute Paths" setting, this option is disabled by default. If you're unsure of the difference between absolute and relative paths, a search or two should clear up any confusion.

[L33THAK0R]

Substantial update was pushed to the repo last night, changelog is as follows:

v2.50 Changelog

New Features

• Jobs Queue Mode: Added a dedicated batch processing queue that handles multiple folders sequentially with automatic checksum generation and detailed status reporting.
• Advanced Options Toolbar: Implemented a toggleable toolbar offering path prefix injection, wildcard file filtering, and directory recursion controls.
• Reset Configuration: Included a help menu option to reset all configuration settings to defaults and automatically restart the application.

Improvements

• Processing Strategy (I/O): Replaced the legacy HDD toggle with a selectable Processing Mode (Auto, HDD, SSD) to override errors in the automatic detection logic.
• Path Storage Logic: Refined path saving behavior with a new Path Storage menu to enforce Relative or Absolute paths and handle cross-drive scenarios correctly.

Bug Fixes

• General Fixes: Fixed critical crashes related to list virtualization and threading race conditions while resolving display inconsistencies between operating modes.

Known Issues

• Currently the new Jobs Mode may cause some slight performance issues, I'm working on resolving these, but I'm satisfied with the state of the current build.
• If you attempt to start a job whilst verifying an existing checksum, this may result in a crash, I'm working on fixing this.

[FitGirl]

Thanks for the tool, but could you also upload "static" build w/o need to install Dotnet for endusers?

[L33THAK0R]

Originally Posted by FitGirl

Thanks for the tool, but could you also upload "static" build w/o need to install Dotnet for endusers?

Unfortunately not, I'm only somewhat alright with high-level languages, I have no experience with low-level languages like C++ & Rust. My current solution searches for the .NET 10 installation at the default path (Assuming C: is the system drive), if not found my installer enables the .NET 10 redist download option (under my redist menu), and installs post-install. It's not perfect but it's the only viable solution I've got currently. C# is an easy language to learn but is mainly designed to work with the .NET runtime/libraries. Maybe down the road I'll look into porting the codebase to something independent, but the costs far outweigh the benefits. Even if using SharpSFV without .NET 10 being installed, there is enough logic embedded in the application to direct the end-user to the appropriate download page.

[Masquerade]

^^
FitGirl means for the .NET runtime to be built into the compiled executable, please see below:
https://stackoverflow.com/questions/...c-sharp-wpf-pr

However in my experience, this leads the compiled file to be 30-40mb in size.

[L33THAK0R]

Originally Posted by Masquerade

^^
FitGirl means for the .NET runtime to be built into the compiled executable, please see below:
https://stackoverflow.com/questions/...c-sharp-wpf-pr

However in my experience, this leads the compiled file to be 30-40mb in size.

Given the 81-298X increase in file size (~110MiB uncompressed, ~30.5MiB compressed (xtool+srep+lolz), versus not including the .NET runtime, I wouldn't even consider this a valid alternative.

[L33THAK0R]

A couple smaller QoL updates, can't think of any additional front-end improvements, or significant back-end optimisations. If anyone has any suggestions or bugs to report, I'll keep an eye on the GitHub issues.

v2.52 Changelog

New Features

• Pause/Cancel Operations: Pause/Cancel buttons are now available for both regular-mode and job-mode.
• Comment Parsing Support: Using the "//" prefix, users can now integrate comments within their checksum files, which will appear in a pinned panel at the top of the main form.

Improvements

• Window Usability: Window dimensions now have a strict minimum size, with a horizontal scrolling bar implemented for easier navigation.
• Window Responsiveness: RunVerification logic has been overhauled to operate in a 2 phase process. Previously the benchmark would take ~119 seconds to complete, versus ~74 seconds on repeat trials, due to Windows caching the Master File Table in memory. I'd overlooked this in testing, it was a hack-job that was never properly addressed. The new logic results in only ~5 seconds of latency versus the previous ~45 seconds.

Bug Fixes

• Performance issues introduced with the "Jobs Mode" feature have been resolved.
• If you attempt to start a job whilst verifying an existing checksum, no crashes will result.

[L33THAK0R]

Merged another project I'd been working on, essentially a stripped down version of SharpSFV that focused on shell integration, mimicking kliu.org's HashCheck utility, but with xxhash3 support. Made a few improvements to the front-end I'd overlooked, as well as a bit of tidying up the back-end, made everything a lot more stable, more streamlined. Quite happy with how it's turning out, outside of course the increased binary size.


v2.6 Changelog

New Features

• Shell Integration: Added Explorer context menu integration with single-instance file queuing and file associations.
• Mini Mode: Created a streamlined UI for context menu operations that automatically saves and exits upon completion.
• CLI Mode: Implemented a -headless argument for command-line usage with console-based progress reporting.
• Taskbar Integration: Added taskbar progress mirroring with color-coded status indicators (Green/Red/Yellow).
• Bad File Tools: Added conditional options to move or rename corrupt files when errors are detected.
• Clipboard Compare: Implemented a feature to instantly verify a selected file against a hash stored in the clipboard.

Performance & Metrics

• Smart Buffering: Optimized I/O performance with dynamic buffer sizing (8MB for HDD, 512KB for SSD).
• Metrics: Added real-time throughput (MB/s) and ETA calculations to the status display.
• Timing: Ensured processing time is tracked internally for all items regardless of column visibility.

User Interface & Experience

• Menu Overhaul: Replaced the Jobs menu with a Mode selector and consolidated Copy actions into a unified "Copy Entry" format, identical to layout seen in generated checksum files.
• Job Mode: Added a Time column to the Job Queue and fixed layout stability issues by disabling incompatible view options.
• UX Improvements: Removed the Stop confirmation prompt and enabled multi-select support for context menu actions.

Fixes & Maintenance

• Bug Fixes: Resolved issues with Job Mode file verification, taskbar progress desyncs, and layout corruption.
• Refactoring: Consolidated UI layout logic into a single class and standardized internal algorithm enumerations.

[L33THAK0R]

Added a very minor v2.61 update, not even really worth patchnotes for, just fixed some edge cases where the legacy SFV support was breaking down. Main purpose of this push was re-writing documentation across every significant class, because Lord knows I'm going to forget how some of this spaghetti code works in the future.