Update VolumeInfo.cs

[SteAmeR]

Issue #23

[SteAmeR]

Any progress?

[EricZimmerman]

i dont have any issues with this, but the concern is, how far do you keep chasing corruption?

[SteAmeR]

Maybe keep strict validation for mandatory structures, but make optional blocks best-effort — skip if corrupted instead of failing the whole parse. This way we don’t chase corruption, we just don’t give up too early :\ So maybe the ideal balance here is:

• Fail-fast for mandatory sections.
• Best-effort for optional blocks — wrap them in try/catch and skip on corruption instead of stopping the whole parse. This way, we don’t “chase” corruption — we just don’t give up too early. It also matches the resilience of the Windows Shell’s native LNK resolver.

[EricZimmerman]

i like this approach. id have to look at the specs to confirm, but what blocks fall under each category?