PB/DLL 6.11 DLL properties question

[Daniel L. Bateman]

Does anyone know how to set the DLL properties that you can see when
you right-click on a DLL file, such as Source, Author, and Revision
Number? Can't find anything here or in the help file.

[Michael Mattias]

Post by Daniel L. Bateman
Does anyone know how to set the DLL properties that you can see when
you right-click on a DLL file, such as Source, Author, and Revision
Number? Can't find anything here or in the help file.

You need to put a VERSIONINFO data block in your resource script.

It will look something like this when you are done:

#define VERSION_MAJOR 0x0002
#define VERSION_MINOR 0x0002
#define VERSION_BUILD 0x0000
#define VERSION_LITERAL "2.2.0"
#define VERSION_DATE "May 26 2003"

VS_VERSION_INFO VERSIONINFO
FILEVERSION VERSION_MAJOR, VERSION_MINOR, 0, VERSION_BUILD
PRODUCTVERSION VERSION_MAJOR, VERSION_MINOR, 0, VERSION_BUILD
FILEOS VOS_WINDOWS32
FILETYPE VFT_APP
//* VFT_DLL FOR DLLs
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904E4"
BEGIN
VALUE "CompanyName", "Tal Systems Inc.\0"
VALUE "FileDescription", "SkelFile\0"
VALUE "FileVersion", VERSION_LITERAL
VALUE "InternalName", "skelfile\0"
VALUE "OriginalFilename", "skelfile.exe\0"
VALUE "LegalCopyright", "Copyright \251 2001 Michael C. Mattias\0"
VALUE "LegalTrademarks", "None\0"
VALUE "ProductName", "skelfile\0"
//OPTIONAL VALUE "ProductVersion", "Version 2.1.0.0 April 2001\0"
VALUE "Comments", "None\0"
VALUE "Author", "M.C.Mattias Racine WI\0"
VALUE "VersionDate", VERSION_DATE
END
END
END


--
Michael Mattias
Tal Systems, Inc.
Racine WI
***@talsystems.com

[Mr. Stabby]

Thanks. I also figured out that you could edit the Properties of a
DLL file in WinXP, not just view them. But a solution to have them in
the program is much better.

[Auric__]

Post by Daniel L. Bateman
Does anyone know how to set the DLL properties that you can see when
you right-click on a DLL file, such as Source, Author, and Revision
Number? Can't find anything here or in the help file.

(Sorry a reply has taken so long; I haven't had an internet
connection for over two months, and I guess no one else is interested
in answering.)

I don't have the DLL compiler, so I don't know whether or not this
will apply (although I assume it does), but in PBWin 7, you have to
make an RC script. It will look something like this:

[begin foo.rc - this line is not part of the file]
1 VERSIONINFO
FILEVERSION 1,0,0,1
PRODUCTVERSION 1,0,0,1
FILEOS 0x4
FILETYPE 0x1
{
BLOCK "StringFileInfo"
{
BLOCK "040904B0"
{
VALUE "FileDescription", "Foo.dll - needed by Foo.exe"
VALUE "LegalCopyright", "Copyright ©2004 My Name"
VALUE "ProductName", "Foo.dll"
VALUE "FileVersion", "1.0.1"
VALUE "ProductVersion", "1.0.1"
VALUE "InternalName", "Foo.dll"
VALUE "OriginalFilename", "Foo.dll"
}
}

BLOCK "VarFileInfo"
{
VALUE "Translation", 0x0409 0x04B0
}
}
[end foo.rc - this line is not part of the file]

Most of that is fairly self-explanatory, I think. I'm *think* that if
you look up resources in the help file, you should get some info - but
since I don't have PB installed on this macheen and I can't currently
access the one that *does* have it, I can't verify that.

Everything within BLOCK "StringFileInfo" is (apparently) optional.
Also, since I based that stuff on an automagically-generated .rc
script, generated by a product that made it from an old VB version of
one of my DLLs, I don't know the legal values of some of that stuff;
"it was just there" and I had no reason to change it.

Anyway, once you have your .rc file written, the IDE should be able to
compile it to what you need - a .pbr file - which you then #include in
you main source file:
#include "foo.pbr" (or whatever it's called)
Compile and you're golden.