Mark Miller

Rob, are you still having trouble here? I've got some motivation to do some work here in the next few months, and I've trying to close some lingering issues.

Yeah, that looks like at least related. Are you writing STDF files, or reading them? From your post, it sounds like you're reading them. Do you have a repro? I...

I am not opposed to doing something like that. I'd want the goals to be clear, and I would want to have full access to the files that don't work....

Thanks for rebasing/bumping this, @JamieMagee ! When I first wrote this, this was very much intended to be a draft to start a conversation on how target framework info could...

It was never a goal for LinqToStdf to round-trip records with a byte-for-byte match. The writer aims to produce standards-compliant STDF files based on the data in the records, not...

I'm re-opening this based on a re-reading of the spec. The section on options fields states [emphasis mine]: > The specification of each STDF record has a column labelled Missing/Invalid...

A quick reading of https://github.com/marklio/LinqToStdf/blob/master/Main/LinqToStdf/RecordConverting/UnconverterEmittingVisitor.cs indicates that the writer incorrectly assumes that any field with the "missing/invalid" value is optional and doesn't pay attention to the IsOptional property. There is...

This is great news. My holidays were jam packed full of unexpected things, so I haven't had time to do anything. All this sounds pretty good. I'll take a look....

Thanks for finding and documenting this fix! I can totally imagine this bug existing. Due to the way that missing data is represented in STDF (records can be truncated at...

oh, weird. I guess it needs more investigation than a guess :)