Version / Company Info Etc.

Hi Rich,

I have more info.
I went to www.stevemiller.net and downloaded and installed depends and that prompted the following.



I did send the following email to Steve Miller and would appreciate it if you have any other ideas. At this point, I can see the version number from my install but, it would be nice to see it from Explorer. By the way, I am including the file in fileview.


Steve,

Thank you. Thank you.

Problem 1 solved. Still could use help with problem 2.

Problem 1: Your dependency walker let me isolate the problem. I changed the project so that the Image version was set using /version link switch as you suggested but, you were right Installshield does not use this. For your edification it uses FileVersion not ProductVersion. I set FileVersion to 1,2,0,1 and ProductVersion 1,2,0,2 and the following snipit:

VerGetFileVersion ( SRCDIR ^ UPDATE_FILE1 , svVersionNumber );
szMsg = UPDATE_FILE1 + " version number check\n";
szMsg = szMsg + "Version Number: " + svVersionNumber;
SprintfBox(SEVERE, szTitle, szMsg);

displayed version number 1.2.0.1


Problem 2: I am still not not seeing the version TAB (that's right not even the TAB) when I look at the properties on the file in explorer. Yes, I can see the version TAB on other files. Please note that the developer that originally created this project is a UNIX developer and he thinks he had "it" create a win32 DLL and he fleshed it out but, he's not sure.

Thanks for all your help
Gary

Are you sure that windows.h is included in your .rc file? That is the only other way I have seen to get RC to compile a version, but have it not show up under properties.

So, you have built your DLL with a Version Resource, and you can check the version info on the DLL with InstallShield, but Windows Explorer doesn't show the Version Tab in Properties? Have you tried using a different machine? One other thing you might try is open your .rc file as text and compare the version info you're compiling into your project with the version info from a .rc file that is known to work. If all else fails, try deleting the version resource and adding a newone. Adding this version stuff to your DLL is really simple, so if I were you, I'd ignore all that stuff about linker options and all that crap and check the basic stuff that should be obvious. Sometimes the answer is there staring you in the face.

Hi Rich,

Just tried this. Still no good.

I did notice that _USRDLL is a preprocessor definition in a DLL I created that works but, when I include that it comes up with a Linker- dup definition of _DllMain

Thanks
Gary

Sorry, I'm rapidly running out of ideas. My inclination in your position would be to create a new DLL project using AppWizard, check the version works in that, then move your code over. It's probably not as long as it sounds to do.