locked
XP and Vista Manifest lists RRS feed

  • Question

  •  

    I should could use some help...  I'm working on a project where most of the software is written in vb6.0.  I've developed an app that generates application and dependent manifests to support reg-free deployment.  My basic problem is when I install (using Altiris 7) my reg free project in vista, I get a syntax error that I don't get with XP.

     

    I've attached a sample of the manifest list for one of my applications:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urnTongue Tiedchemas-microsoft-com:asm.v1"  manifestVersion="1.0">
    <assemblyIdentity type="Win32"
       name="ChangeRegistry.exe"
       version="1.0.0.16"
       processorArchitecture="x86" />

    <file name = "C:\\Program Files\\ClubTec\\bin\\ChangeRegistry.exe"/>

    <dependency>
     <dependentAssembly>
      <assemblyIdentity processorArchitecture="x86"
         type="win32"
         name="ctcADOClone.dll"
         version="2.0.0.1"/>
     </dependentAssembly>
    </dependency>

    </assembly>

    In the above example, the bolded line "<file name ="... works just fine with XP.  But when I try this same application on a vista OS and even a Windows 2003 Server, I get a syntax error on the bolded line

     

    I've tried such things as <file name = "C:\Program Files\ClubTec\bin\ChangeRegistry.exe"/>

    which doesn't work.

     

    I have to have the pathing as part of this element.  The software is built in such a way that each major executable has it's own directory and the dlls and ocx's are in a "bin" folder.  the heirarcy looks like:

     

    Program files\<Company>\<App1>\

    Program files\<Company>\<App2>\

    Program files\<Company>\bin\

     

    <app1> is the first application

    <app2> is another application

    bin is the location of the "common" components

     

     

    Finding the pathing information took days to find, I need to find what will work in Vista.

     

    Thanx

     

    Kyle

     

     

    Friday, September 12, 2008 8:30 PM

All replies

  • Is <file> part of the schema schemas-microsoft-com:asm.v1?

    Friday, September 12, 2008 9:54 PM
  • No it's not.  The "<file" element actually starts the definition of any com classes and the type library.  Here's a different manifest file that shows a more robust manifest list

     

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urnTongue Tiedchemas-microsoft-com:asm.v1"  manifestVersion="1.0">
    <assemblyIdentity type="Win32"
       name="ctcADOMTS.dll"
       version="1.1.0.0"
       processorArchitecture="x86" />

    <file name = "C:\\Program Files\\ClubTec\\bin\\ctcADOMTS.dll">

     <comClass description="ctcADOMTS.CMTSData"
       clsid="{1D4C50F0-17E4-43CF-B3DD-186BA6CF6ABB}"
       progid="ctcADOMTS.CMTSData"
       threadingModel="Apartment"/>

     <comClass description="ctcADOMTS.CParm"
       clsid="{9673FC12-656A-4D26-B18C-5C3FF8F0680B}"
       progid="ctcADOMTS.CParm"/>

     <comClass description="ctcADOMTS.CParms"
       clsid="{2E06DA43-8481-4F87-BDF0-BD8407FCDF58}"
       progid="ctcADOMTS.CParms"/>

     <typelib tlbid="{3FA9F93E-03D2-4E3B-8B10-605E42B4A84B}"
       version="1.1"
       helpdir="C:\Program Files\ClubTec\bin"/>
    </file>

    </assembly>+

     

    Monday, September 15, 2008 3:52 PM