Win32 Version Info Updater and DLL projects

I'm using the Win32 Version Info Updater action to update some .rc files for a Visual Studio 6 project. The project in question is for a .dll and the rc file before the action is run has  FILETYPE  0x2L (meaning the data is a DLL) and the action (which works perfectly for updating the FileVersion and ProductVersion is changing FILETYPE to 0x1L (meaning the data is an application).

1) I'm not sure if this is necessarily a bug report (so I'm posting in this forum), Is there something I should know about this action?

2) Is this FILETYPE change going to impact anything on any scale that I should care? I know that this data is used by certain win32 api calls that get information about a file. If the dll still builds as a dll, registers properly and functions, is there any other mechanism that this may cause a problem with?

3) FinalBuilder is great!

Hi Daniel,

Thanks for the post.

1) Your instincts are right that it's a bug. Some of the actions which update RC files let you specify whether it's a DLL or not, but the Win32 action doesn't so it should respect the current value. We have a fix checked in, I'll let you know when there's a test build available.

2) I don't explicitly know of anything that it will impact, it might be an anachronism (Raymond Chen doesn't seem to have blogged about it, and he's the best source I know for info about Windows' arcane details.) It obviously can't hurt to have it set correctly, though.

3) I agree, thanks for the post. :-).

Regards,

Angus