Skip to content

fix: fixes an mspack issue with a cab - #8

Open
activescott wants to merge 1 commit into
masterfrom
fix/lessmsi-194-cabinet-sets
Open

fix: fixes an mspack issue with a cab#8
activescott wants to merge 1 commit into
masterfrom
fix/lessmsi-194-cabinet-sets

Conversation

@activescott

@activescott activescott commented Jun 16, 2024

Copy link
Copy Markdown
Owner

I expect this to fix or at least partially fix activescott/lessmsi#194 . Doing some more testing locally before merging

Also updates to make it compile and test with VS 2022; Remember to use the x86 Native Tools Command Prompt for VS 2022.

Tasks:

…si#193

also updates to make it compile and test with VS 2022; Remember to use the *x86* Native Tools Command Prompt for VS 2022
cab->base.prevname = cabd_read_string(sys, fh, &err);
if (err) return err;
cab->base.previnfo = cabd_read_string(sys, fh, &err);
// in at least one CAB the nextname was set but nextinfo was empty; so we allow an empty nextinfo here

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: This is the core fix here on the mspack side. Some of these multipart cabs seem to have empty nextinfo's and we need to safely ignore that

Comment thread libmspack4ntest/Basic.cs
foreach (var f in files)
ExplodeCab(f);
var root = TestFilesPath;
string[] files = Directory.GetFiles(root, "*.cab");

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

todo: fix formatting. Why does vs allow this?

@activescott activescott self-assigned this Jul 12, 2024
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.

Doing "Extract" on this MSI file produces no results

1 participant