Results 1 to 5 of 5
  1. #1
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    vb6 - 'binary compatibility' (vb6)

    How do I turn off "Binary Compatibility"?

    I am essaying to recompile a suite of DLLs, OCXs and EXEs from a suite of VBPs.

    I compile about six modules, and then one VBP sparks up "The binary compatibility DLL or EXE contains a parameter type or return type whose definition can not be found".

    A search on the web points heaviliy towards ADO libraries.


    I understand the need for backward compatibility when developing general-purpose libraries in DLL form, but in my case I want ONLY (today) to recompile existing source to satisfy ourselves that the supplied source will indeed produce a single useable executable. At that point we can agree to purchase the code and start serious work.

    I'd like, just for this week, to bypass all sorts of safeguards, where MSoft is looking after my future interests, so that I can tell my client that they appear to have all the necessary source.



    Is the problem likely to be in the VBP I am currently trying to compile, or is it more likely to be in one of the first few modules I have just compiled and which is being used via the Project references scheme?

  2. #2
    New Lounger
    Join Date
    Jan 2001
    Location
    Chicago, Illinois, USA
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - 'binary compatibility' (vb6)

    Chris,

    The compatibility options are found under Project * Project Properties * Component * Version Compatibility. You can change it with the option button.

    Rex

  3. #3
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - 'binary compatibility' (vb6)

    Thanks, Rex.

    Given that my DLLs are aimed at only my code (I'm not writing general-purpose DLLs for the public), if i change compatibility from Binary to project, or even to "None", amd I likely to cause myself problems?


    My plan is to map out dependencies of modules, and use the tried-and-trusted method of recompiling all modules which make use of any module which has suffered a change, so I expect that my compiled stuff will always be updated after a coding change.

  4. #4
    New Lounger
    Join Date
    Jan 2001
    Location
    Chicago, Illinois, USA
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - 'binary compatibility' (vb6)

    <P ID="edit" class=small>Edited by gwhitfield on 18-Jan-02 06:56.</P>Hyperlinks added

    Chris,

    As long as your re-compiling at each step, I can't think of any issues. I will admit, I'm not very experienced in this area. You may want to take a look at this article at TechRepublic, Demystifying version compatibility settings in Visual Basic <A target="_blank" HREF=http://www.techrepublic.com/article.jhtml?id=r00820010309adm01.htm>http://www.techrepublic.com/article.jhtml?...010309adm01.htm</A>.

    Cheers,
    Rex

  5. #5
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - 'binary compatibility' (vb6)

    Thank you for the link (and Thanks Geoff for the edit). I will read the notes and get going.

    My suspicion is that a self-contained project won't need it as long as everything gets recompiled.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •