cableguy67 wrote:
>> I think Greg posted some comments before on what he'd done to work
>> with/around M$'s latest and greatest impediment to clarity and
>> understanding. But I can't find them now.
>> I vaguely recall he may have reverted to VC6 and just ignored the whole
>> manifest/installer business in the end though...
> 
> http://www.fltk.org/newsgroups.php?gfltk.opengl+v:1179

        Yep, that's the one.

D. Zimmer wrote:
>> I have been taught over the last three days that I *must* use the
>> Microsoft Installer via an MSI file.
> 
> Not true.  You can instruct the user to run vcredist_x86.exe first,
> then the app can be run from any folder without installation.

        Yes, this sounds like the "new" Microsoft compilers, with its
        manifest requirements, etc. The new stuff is all in the name
        of security, I think.

        "DLL Hell" was tame by comparison to the new hoops MS wants
        us to jump through.

        Running that little tool as part of install helps get things
        working, in addition to correct manifest configurations,
        'side-by-side' DLL deployment, etc.


> see http://www.pcreview.co.uk/forums/thread-1544611.php

    I love this excerpt from the poor sysadmin:

---
        "The advertised application will not be installed because
        it might be unsafe. Contact your administrator to change
        the installation user interface option of the package to basic."

        I'm the administrator and I have no idea what this means.
---

    LOLZ. Poor guy.

    Sysadmins lives are hard enough, now they are burdened by
    messages like this (Contact your administrator, who will be
    as confused as you are). Admins now have to know about obscure
    tweaking tools like "orca" to modify MSI files:

        If you take a look at your MSI using a tool like Orca,
        you should find the following in the Property table:

        VSDUIANDADVERTISED This advertised application will not
        be installed because it might be unsafe. [..]

        If you then go to the CustomAction table, you'll find
        the following row for a type 19 custom action that makes
        use of this error message:

        ERRCA_UIANDADVERTISED 19 [VSDUIANDADVERTISED]

        If you then look in your InstallUISequence table, you'll
        find the following row: ERRCA_UIANDADVERTISED ProductState=1 1
        [..]
        -- Microsoft Windows Installer Team

    ..oh yeah, "type 19 custom action", "ERRCA_UIANDADVERTISED"..
    of course! ;)

    BTW, the 'MSI FAQ' link in MS's response is stale.
    The new "link de jours" (that'll probably be stale tomorrow) is:
    http://www.microsoft.com/technet/community/en-us/management/msi_faq.mspx
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to