Rob, that's why I said : " I'm working on a boostrapper which really needs elevated privileges in order to completely install our solution. ( I know I normally shouldn't do that, but we don't have choice because of the specific components needed to be install ). "
So, is there a way to alter / driver / update the Bundle manifest before generation or once generated ? On just include a resource file into the Bundle project (as in normal projects), in order to control the executable manifest ? Please, I understood your point of view, and the fact you have to drive the way people uses WiX, but we only have this option in order to manipulate the elements we need to manipulate. We are in production environments, and using really specific technologies, all is working fine except the fact we have to put a message saying "you must run this "as administrator" because we have no way at the moment to just modify the manifest of the generated bundle executable... We just need to put a <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> into this manifest... In order to give a "normal" / "usual" user experience... (think about nullsoft for example, I believe there is no restriction at this level) Hoping you can drive us to a working workaround... Bests, -------------------------------- Re: [WiX-users] Bootstrapper manifest From: Rob Mensching <r...@robmensching.com> - 2013-01-08 14:17 Subject: Re: [WiX-users] Bootstrapper manifest Your BootstrapperApplication should not be modifying machine state at all. Machine state changes should be in "packages" (MSI, EXE, MSP, etc.) that are listed in the Bundle/Chain element. Your BA can then control which packages are installed. Raphael DUCOM Développeur Tel : | Fax : +33 979 999 341 Web : www.prodware.fr -----Message d'origine----- De : Raphael DUCOM Envoyé : mardi 8 janvier 2013 09:58 À : wix-users@lists.sourceforge.net Objet : Re: Bootstrapper manifest Hi Rob, Many Thanks for your answer, but I believe I didn't give a good explanation... When you say "put stuff that modifies the machine in the Chain and elevate", I think you mean "using a custom action which elevates" like <CustomAction .... Execute="deferred" Impersonate="no" /> isn't it ? My scenario is different, I use the BootstrapperApplication class in order to implement our custom installer, and lot of specific actions are implemented inside our UI installer and not as CustomActions. This installer UI also drives the installation of msi via the wix Engine. So I need a way to elevate the process which instantiate and run the BootstrapperApplication class, not CustomAction. And for instance, I believe the only way is to alter / update the bootstrapper exe manifest. Is there a way to do that ? Thanks in advance, Bests, Raphael DUCOM, -------------------------------- Date: Mon, 7 Jan 2013 06:06:41 -0800 From: Rob Mensching <r...@robmensching.com> Subject: Re: [WiX-users] Bootstrapper manifest Burn will elevate the install much the same way that the Windows Installer elevates the install. Make sure you put all your stuff that modifies the machine (aka: requires elevation) in the Chain and it will be elevated. On Mon, Jan 7, 2013 at 3:27 AM, Raphael DUCOM <rdu...@prodware.fr> wrote: > Hello, > > I'm working on a boostrapper wich really needs elevated privileges in > order to completly install our solution. (I know I normally should'nt > do that, but we don't have choice because of the specific components > needed to be install). > I'm searching a way to define a specific manifest file for a generated > bootstrapper executable. > I'm aware of the already answered forum posts (in 2011) : > - > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Manifest > -for-Burn-Bootstrapper-td6605859.html > - > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-how > -to-elevate-BA-Manifest-for-Burn-Bootstrapper-Continue-td6855345.html > > I have tried embed manifest with mt.exe with no success, same error as > the second post. (mt.exe : general error c101008c: Failed to read the > manifest from the resource of file "C:\ ..... > MyInstall_1.0.107.41.exe.manifest". > The binary is not a valid Windows image.) I also have tried the > Elevate() function of BA, which doesn't elevate the context at all. > > But when looking in depth to my generated executable with Mitec EXE > Explorer, I found there is a manifest embed into it (you will fin dit > at the end of this mail) > > My question is : > - Is there a way to embed or define a manifest with more recent (3.7) > version of WiX while generating a Bundle EXE ? (with specific candle > or light parameters ?) > - Is it possible to alter or modify the manifest once the bundle > executable is generated ? (with mage.exe ?) > - Is there a workaround other than "no, you just don't have to elevate > privileges" ? > > Thanks in advance, we are really stuck on this... > > Bests, > Raphael DUCOM ________________________________ ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
