[RESOLVED] DWord Alignment of VB Resource File Entries

[LaVolpe]

I've seen posts regarding this topic from time to time. So, trying to get a definitive answer from you guys/gals from your personal, verifiable experiences.

Can VB change the reported actual size of an individual resource once it is compiled into the application?

FYI. I know that prior to SP6, this was a bug and supposedly fixed with SP6. That bug resulted in VB padding the resource, as needed, 1 to 3 vbNullChar bytes to force dword alignment. That in itself is not the problem, the problem is if the size of the resource was adjusted to match. This bug appears primarily with HTML/XML resources (RT_HTML/RT_MANIFEST respectively). The resource size includes the null characters and null characters are not valid in that context.

Note: I've seen a couple of Elroy's posts regarding this topic, but do not know if they were pre-SP6 or not. In his case, his concern was checksums/CRCs when extracting data from a resource to file. If the resource was padded and size was modified to reflect the padding, then the extracted resource would be 1-3 bytes larger than original; resulting in a failed checksum/CRC validation.

Edited: msdn comments about the pre-SP6 padding bug