coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

I'm building a tool that creates a number of EXEs (in C) and a number of DLLs.

Each EXE is linked to one or more DLLs

Each DLL can be linked to zero or more DLLs

I can create several versions a DLLs, so that some things depend on newer versions
and I can tell some DLLs to be 'binary-compatable' to older ones, and some are not

I'm trying to figure out how many EXEs to create. How many DLLs each of the EXEs is linking to, and what versions of each
so that I cover as many combinations as possible.

Each EXE & DLL will have a single function (say 'Lib[DLLNAME]_print()') that prints an XML fragment that tells "what it is" , "what version it is" and all of its dependencies'.

(so it's recursive)

example output:

    <pgm name="EXE_A" version="1.0.0.0">
        <lib name="LIB_A" version="1.0.2.0" />
    </pgm>

and:

    <pgm name="EXE_B" version="1.0.0.0">
        <lib name="LIB_B" version="2.1.2.0" >
            <lib name="LIB_C" version="1.1.1.1" />
        </lib>
    </pgm>

and:

    <pgm name="EXE_C" version="1.0.0.0">
        <lib name="LIB_B" version="2.1.2.0" >
            <lib name="LIB_C" version="1.1.1.1" />
        </lib>
        <lib name="LIB_D" version="5.0.33.44" />
    </pgm>


etc....

How do I drive my funky creator to generate all the package combinations that we want to test?

I want to generate EXEs and DLLs that depend on different versions of DLLs, some should be binary-compitable, some not (so we'd see two different versions of the same library loaded by the same EXE at some point).

I've got the code ready to generate, compile, sign EXEs and DLLs, so they can be turned into WinSXS assemblies, I just need a formula.

Any ideas?

G