Welcome, Guest! Log in | Create account

Email Archive: wix-users (read-only)

2004:
 Jan
    		Feb
    		Mar
    		Apr
(98) 		May
(256) 		Jun
(66) 		Jul
(104) 		Aug
(74) 		Sep
(177) 		Oct
(309) 		Nov
(330) 		Dec
(377)
2005:
 Jan
(268) 		Feb
(304) 		Mar
(337) 		Apr
(396) 		May
(516) 		Jun
(588) 		Jul
(475) 		Aug
(371) 		Sep
(460) 		Oct
(549) 		Nov
(465) 		Dec
(312)
2006:
 Jan
(510) 		Feb
(656) 		Mar
(581) 		Apr
(465) 		May
(561) 		Jun
(593) 		Jul
(617) 		Aug
(663) 		Sep
(684) 		Oct
(840) 		Nov
(712) 		Dec
(598)
2007:
 Jan
(857) 		Feb
(695) 		Mar
(1040) 		Apr
(1109) 		May
(1094) 		Jun
(949) 		Jul
(941) 		Aug
(808) 		Sep
(760) 		Oct
(906) 		Nov
(693) 		Dec
(497)
2008:
 Jan
(752) 		Feb
(638) 		Mar
(679) 		Apr
(878) 		May
(1049) 		Jun
(886) 		Jul
(951) 		Aug
(747) 		Sep
(884) 		Oct
(1359) 		Nov
(924) 		Dec
(881)
2009:
 Jan
(1055) 		Feb
(1096) 		Mar
(783) 		Apr
(826) 		May
(845) 		Jun
(928) 		Jul
(317) 		Aug
    		Sep
    		Oct
    		Nov
    		Dec
   
From: John-Daniel Trask <jd@mi...> - 2008-07-31 01:26
Hi,



We have built a Visual Studio package that we are integrating using WIX.



I've run into issues however as we need to run as an administrator. I
applied the required changes to make this work (elevated install privilages,
the custom action that calls devenv /setup was set to before finalize, the
action is deferred and not impersonated). However while this action
completes it doesn't integrate properly and I get COM errors with anything
relating to menu entries and my package in Visual Studio despite no errors
during the install process.



When I actually run the MSI using the awkward run-as-admin method of calling
msiexec directly, it works. Something we can't really ask our customers to
do.



I explored the WIX output that Visual Studio automatically generates for
Visual Studio packages it has the comment that devenv /setup needs to be
called after finalize as if anything is getting GAC'd it won't be available
until that point.



However, my understanding is that the elevated privileges don't get carried
over if done after finalize which is the problem we're seeing here. If my
action gets called before finalize it fails (so it would seem that the
comment in the generated wix document is correct).



Is there any way of extending the elevated privileges after finalize?



The closest thing I can find about this issue is here:
http://www.mail-archive.com/wix-users@li.../msg12030.html



Any help or advice would be greatly appreciated as this problem is reaching
that painful point of frustration! :-)



John-Daniel Trask

Director

MINDSCAPE


Phone:

+64 21 434 957


Web:

mindscape.co.nz


Blog:

<http://blog.bluecog.co.nz> blog.bluecog.co.nz


    From: Rob Mensching <Rob.Mensching@mi...> - 2008-07-31 15:41
    The WiX3.msi registers with VS. I'm not an expert in that stuff but how is yours different than what the WiX toolset does?

    -----Original Message-----
    From: wix-users-bounces@li... [mailto:wix-users-bounces@li...] On Behalf Of John-Daniel Trask
    Sent: Wednesday, July 30, 2008 18:26
    To: wix-users@li...
    Subject: [WiX-users] UAC + devenv setup

    Hi,



    We have built a Visual Studio package that we are integrating using WIX.



    I've run into issues however as we need to run as an administrator. I
    applied the required changes to make this work (elevated install privilages,
    the custom action that calls devenv /setup was set to before finalize, the
    action is deferred and not impersonated). However while this action
    completes it doesn't integrate properly and I get COM errors with anything
    relating to menu entries and my package in Visual Studio despite no errors
    during the install process.



    When I actually run the MSI using the awkward run-as-admin method of calling
    msiexec directly, it works. Something we can't really ask our customers to
    do.



    I explored the WIX output that Visual Studio automatically generates for
    Visual Studio packages it has the comment that devenv /setup needs to be
    called after finalize as if anything is getting GAC'd it won't be available
    until that point.



    However, my understanding is that the elevated privileges don't get carried
    over if done after finalize which is the problem we're seeing here. If my
    action gets called before finalize it fails (so it would seem that the
    comment in the generated wix document is correct).



    Is there any way of extending the elevated privileges after finalize?



    The closest thing I can find about this issue is here:
    http://www.mail-archive.com/wix-users@li.../msg12030.html



    Any help or advice would be greatly appreciated as this problem is reaching
    that painful point of frustration! :-)



    John-Daniel Trask

    Director

    MINDSCAPE


    Phone:

    +64 21 434 957


    Web:

    mindscape.co.nz


    Blog:

    <http://blog.bluecog.co.nz> blog.bluecog.co.nz



    -------------------------------------------------------------------------
    This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
    Build the coolest Linux based applications with Moblin SDK & win great prizes
    Grand prize is a trip for two to an Open Source event anywhere in the world
    http://moblin-contest.org/redirect.php?banner_id=100&url=/
    _______________________________________________
    WiX-users mailing list
    WiX-users@li...
    https://lists.sourceforge.net/lists/listinfo/wix-users

    From: Bob Arnson <bob@jo...> - 2008-07-31 16:09
    John-Daniel Trask wrote:
    > I explored the WIX output that Visual Studio automatically generates for
    > Visual Studio packages it has the comment that devenv /setup needs to be
    > called after finalize as if anything is getting GAC'd it won't be available
    > until that point.
    >

    You can try a commit, no-impersonate custom action but there's no
    guarantee that GAC'd resources will be available; that's just the nature
    of the two-phase commit and hand-off between MSI and Fusion.

    --
    sig://boB
    http://joyofsetup.com/

    From: John-Daniel Trask <jd@mi...> - 2008-07-31 22:35
    I've tried this and it appears to work.

    You mention there is no guarantees with this process. Does this mean there
    would be a more robust mechanism of achieving the same outcome? Would
    bootstrapping and then manifesting the bootstrapper in a manner that
    elevated permissions resolve this issue more?

    If this is just how people have been achieving a positive outcome with no
    promises that it will always work, that's acceptable for now but if the
    install process doesn't work we run the possibility of losing a sale so I'm
    happy to invest more time in a more robust solution if there is one :-)

    Thanks for your advice Bob.

    - JD

    On Fri, Aug 1, 2008 at 3:51 AM, Bob Arnson <bob@jo...> wrote:

    > John-Daniel Trask wrote:
    > > I explored the WIX output that Visual Studio automatically generates for
    > > Visual Studio packages it has the comment that devenv /setup needs to be
    > > called after finalize as if anything is getting GAC'd it won't be
    > available
    > > until that point.
    > >
    >
    > You can try a commit, no-impersonate custom action but there's no
    > guarantee that GAC'd resources will be available; that's just the nature
    > of the two-phase commit and hand-off between MSI and Fusion.
    >
    > --
    > sig://boB
    > http://joyofsetup.com/
    >
    >
    >
    > -------------------------------------------------------------------------
    > This SF.Net email is sponsored by the Moblin Your Move Developer's
    > challenge
    > Build the coolest Linux based applications with Moblin SDK & win great
    > prizes
    > Grand prize is a trip for two to an Open Source event anywhere in the world
    > http://moblin-contest.org/redirect.php?banner_id=100&url=/
    > _______________________________________________
    > WiX-users mailing list
    > WiX-users@li...
    > https://lists.sourceforge.net/lists/listinfo/wix-users
    >

    From: Bob Arnson <bob@jo...> - 2008-08-01 15:42
    John-Daniel Trask wrote:
    > You mention there is no guarantees with this process. Does this mean there
    > would be a more robust mechanism of achieving the same outcome? Would
    > bootstrapping and then manifesting the bootstrapper in a manner that
    > elevated permissions resolve this issue more?
    >

    Nope, it's not a permissions problem. Basically, the problem with commit
    custom actions is that they rely on MSI's rollback support being
    enabled; it is by default, but it can be disabled. When rollback is
    disabled, commit custom actions are just skipped with no errors. In that
    situation, your VSPackage won't be registered at all. The guidance to
    put VSPackages in the GAC should carry big disclaimers. In general, a
    private assembly in some Program Files directory is the best because it
    won't have the risks with the GAC.

    --
    sig://boB
    http://joyofsetup.com/

About SourceForge

Find Software

Develop Software

Community

Help

Copyright © 2009 SourceForge, Inc. All rights reserved. Terms of Use