Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

TARGETTYPE MSI

Aram_Havarneanu-2Aram_Havarneanu-2 Member Posts: 161
After looking at the WDK Makefiles, I have found that the build tools
have an undocumented MSI TARGETTYPE. Anybody using this? It would help
me a lot to be able to build a full release (exactly the product the
client will get) with a single build command.

Anybody has any idea on how to use this?

Thanks,

--
Aram Hăvărneanu

Comments

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,435
    Not supported, there are no msi tools shipped with the wdk. Your best bet is to use the WiX tools and invoke them after build, or if you want it to be a part of the build process itself, make it a custom pass2 action using a makefile.inc rule

    d

    tiny phone keyboard + fat thumbs = you do the muth



    -----Original Message-----
    From: Aram H?v?rneanu <xxxxx@mgk.ro>
    Sent: Sunday, March 28, 2010 8:16 AM
    To: Windows System Software Devs Interest List <xxxxx@lists.osr.com>
    Subject: [ntdev] TARGETTYPE MSI


    After looking at the WDK Makefiles, I have found that the build tools
    have an undocumented MSI TARGETTYPE. Anybody using this? It would help
    me a lot to be able to build a full release (exactly the product the
    client will get) with a single build command.

    Anybody has any idea on how to use this?

    Thanks,

    --
    Aram H?v?rneanu

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
    d
  • Aram_Havarneanu-2Aram_Havarneanu-2 Member Posts: 161
    2010/3/28 Doron Holan <xxxxx@microsoft.com>:
    > Not supported, there are no msi tools shipped with the wdk. Your best bet is to use the WiX tools and invoke them after build, or if you want it to be a part of the build process itself, make it a custom pass2 action using a makefile.inc rule

    That is exactly what I am doing now, except that I don't use WiX, I
    use NSIS. It works well, but it's another *independent* thing you have
    to manage... In the default config, for another developer to work on
    my code he'd have to have NSIS installed exactly like I do, so I
    actually bundle NSIS in my tree so I have a local copy that is called
    by nmake as needed. It's better, but the best would be to have
    everything integrated by default.

    Completeness and the static behaviour of tools (*) I think it's very
    valued by developers. I think I read a document written by Mark
    Lucovsky about some internal refactorings in Windows in Windows 2000
    timeframe that stated that the build tools are complete to the point
    that you only need the build environment to produce a working windows
    release on a developer's machine. That is good stuff.

    (*) By static behaviour of tools I mean that the developer should
    never alter any part of the build tools. They should work from a read
    only network share. This is not true today. You need to alter build
    tools shortcuts to properly use BinPlace.

    --
    Aram Hăvărneanu
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA