Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix "Not a valid Win32 FileTime" exception #35

Merged
merged 5 commits into from
Mar 31, 2024
Merged

Fix "Not a valid Win32 FileTime" exception #35

merged 5 commits into from
Mar 31, 2024

Conversation

FreeTheTech101
Copy link
Contributor

According to the documentation for minwinbase.h, Win32 apps (and therefor Windows itself) can only handle date times as early as January 1st, 1601. However, .NET can handle date times as early as January 1st, 0001, resulting in an exception being thrown. To solve this, we now clamp the value returned by the AsDateTime function.

This merge also bumps the target framework from .NET Core 3.0 to .NET 8, and re-targets Windows 10, mostly for ease of installation, as .NET Core 3.0 is no longer supported.

RezTech added 2 commits March 13, 2024 20:53
Bump FATX to target netstandard2.1
Bump FATXTools to target .NET 8 and Windows 10
Bump System.Text.Json to 8.0.3
Fix crash when attempting to dump incorrectly parsed files
@aerosoul94
Copy link
Owner

Would you mind updating the build pipeline please? I believe you might just need to update the .net version here: https://github.com/aerosoul94/FATXTools/blob/master/.github/workflows/build.yaml#L23

Update .NET actions from .NET Core 3.0 to .NET 8.0
@FreeTheTech101
Copy link
Contributor Author

Based on this GitHub support page for Actions, there is probably a better way of doing this. However, for now this should be "good enough".

Further fixes for invalid time stamps. Although the original patch was enough to get this working in my case, it seems this is required for others
Update actions/checkout from v2 to v4
Update microsoft/setup-msbuild from v1.0.2 to v2
@FreeTheTech101
Copy link
Contributor Author

Seems that the original patch was not enough to fix this issue for all users, so here we go with round two. I've also gone ahead and updated the other pipeline dependencies to reduce the number of warnings.

@aerosoul94
Copy link
Owner

Looks good. Ready to be merged?

@FreeTheTech101
Copy link
Contributor Author

Yup, all good to merge!

@aerosoul94 aerosoul94 merged commit 99a1937 into aerosoul94:master Mar 31, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants