Indigo Rose Software

Professional Software Development Tools

 
Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2007
    Posts
    1

    Unable to see/add dependency modules on XP

    We have been trying to make use of the .NET 2.0 dependency module and subsequently experimented with others, but when going to Resources -> Add, the ONLY modules that appear are the two included ones for VB. Is there another setting or location that must be modified for Setup Factory 7.0.6.1 to dynamically pick up newer dependencies? We notice the two VB ones do not have xml files whereas the ones we cannot get to appear have an xml file with the same name as the subdir it appears in under dependencies.

    Code:
    Sample hierarchy on my machine:
    c:\Setup Factory 7.0\Dependencies\
      dotnet2_0\
        dotnet2_0.xml
        dotnetfx.exe
      mdac28sp1\
        mdac28sp1.xml
        WGAPluginInstall.exe
      vb5sp3\
        Msvbvm50.exe
      vb6sp6\
        VBRun60sp6.exe

  2. #2
    Join Date
    Mar 2005
    Location
    WA 'wait a while' - Australia
    Posts
    872
    Hi there,

    for modules to be accessable, the actual .xml file for any module
    needs to live in ROOT\ of the dependancies folder of the SUF70
    installation on your system.

    eG: Dependancies\dotnet2_0.xml

    If SUF70 is running and a new module is manually added,
    SUF70 needs to be closed and restarted to recognise the addition

    (the runtime itself , the .exe, can actualling live anywhere on a system
    as there is option to select the file location during module editing.)

    currently there is no option to 'import' - browse-select a dependancy module.xml from another location

    hth
    Last edited by Eagle; 04-05-2007 at 04:09 PM.

  3. #3
    Join Date
    Mar 2005
    Location
    WA 'wait a while' - Australia
    Posts
    872
    additional info, modules when added for use are treated as 'templates'
    so any modification to a selected module for a loaded project is 'saved'
    in the project file and for that project build only.

    This way the 'original' module.xml file is protected from changes.

    The module 'export' or module 'new' options are the way to go to
    save\create fresh 'project independant' 'module templates'.

    fwiw some of the 'howto' download and 'where to put a new module'
    to make it available for use are not accurate, creating confusion.

    if not already, maybe IR could have a fresh look at the whole Module
    creation-addition functionality, howto thing.
    Last edited by Eagle; 04-05-2007 at 04:41 PM.

Similar Threads

  1. Dependency Module: Microsoft .NET Framework 2.0
    By Adam in forum Setup Factory 8.0 Examples
    Replies: 30
    Last Post: 11-20-2009, 08:27 PM
  2. Dependency Module: Microsoft .NET Framework 1.1
    By Darryl in forum Setup Factory 8.0 Examples
    Replies: 12
    Last Post: 06-10-2008, 02:26 AM
  3. Dependency Modules
    By Tipperton in forum Setup Factory 7.0
    Replies: 5
    Last Post: 07-28-2006, 11:17 AM
  4. Dependency Module: MyODBC 3.51
    By TerryRogers in forum Setup Factory 8.0 Examples
    Replies: 1
    Last Post: 04-05-2006, 10:27 AM
  5. Dependency Modules
    By ghostrock in forum Setup Factory 7.0
    Replies: 3
    Last Post: 03-15-2006, 03:46 PM

Posting Permissions

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