Announcement

Collapse
No announcement yet.

The use of Version information in PB Dlls

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Egbert Zijlema
    replied
    Scott,

    Do you know, by the way, how to get the content of "Companyname" visible by default?
    So without the need to click on it?
    See a few "version" tabs of Microsoft programs to know what I mean.
    And further more: what are the possible values. For instance, Microsoft itself uses Language.

    ------------------

    Leave a comment:


  • Edwin Knoppert
    replied
    Note that i ALLWAYS check the binary version NOT the text version.

    VS_VERSION_INFO VERSIONINFO
    >FILEVERSION 1, 4, 1, 0
    > NOT! VALUE "FileVersion", "04.11\000"


    ------------------
    [email protected]

    Leave a comment:


  • Egbert Zijlema
    replied
    Thank you!
    It was not easy yet. Did not know the rc-compiler is case-sensitive, so #INCLUDE generated a fatal error.
    In the meantime I included this sort of info in: http://www.basicguru.com/files/zijle...l60/easter.zip

    ------------------


    [This message has been edited by Egbert Zijlema (edited July 01, 2000).]

    Leave a comment:


  • Troy King
    replied
    Originally posted by Egbert Zijlema:
    RC.EXE reports an 'undefined keyword or keyname VOS_WINDOWS32'.
    The routine works, but you have to make sure you've defined VOS_WINDOWS32. The easiest way to do that is to just include resource.h in the resource file. Just add
    Code:
    #include "resource.h"
    to the top of your resource file, and copy the resource.h from the PB \winapi directory to the directory with your resource file. It will work then.



    ------------------
    Troy King
    [email protected]

    Leave a comment:


  • Egbert Zijlema
    replied
    This routine does not work.
    RC.EXE reports an 'undefined keyword or keyname VOS_WINDOWS32'.
    What's wrong?

    Egbert

    ------------------

    Leave a comment:


  • Graham McPhee
    replied
    Thanks for the information on inserting the version in a DLL, it's just what I was looking for.

    Leave a comment:


  • Scott Turchin
    replied
    I do it in the resource file:
    Change Application to Dyanimic Link Library or whatnot ...
    Code:
    VS_VERSION_INFO VERSIONINFO
    FILEVERSION 1, 4, 1, 0
    PRODUCTVERSION 1, 4, 1, 0
    FILEOS VOS_WINDOWS32
    FILETYPE VFT_APP
    BEGIN
      BLOCK "StringFileInfo"
      BEGIN
        BLOCK "040904E4"
        BEGIN
          VALUE "CompanyName",      "Computer Creations Software\000"
          VALUE "FileDescription",  "Application\000"
          VALUE "FileVersion",      "04.11\000"
          VALUE "InternalName",     "Winlog98/NT\000"
          VALUE "OriginalFilename", "WINLOG.EXE\000"
          VALUE "LegalCopyright",   "Copyright (c) 1997-1999 Computer Creations Software\000"
          VALUE "LegalTrademarks",  "\000"
          VALUE "ProductName",      "Winlog For Windows 98/NT\000"
          VALUE "ProductVersion",   "04.11\000"
        END
      END
    END

    Run rc and pbres against it and use a $resource "appname.pbr" and you're in business.


    Scott

    -------------
    Scott Turchin


    Leave a comment:


  • Graham McPhee
    started a topic The use of Version information in PB Dlls

    The use of Version information in PB Dlls

    How do you insert file version information into a PB DLL?
    I need this to ensure correct installation using the WISE
    instalation package.
Working...
X