Re: [WiX-users] MSI error 1935 (0x80070003) installing sharedWin32 assembly - but only when installer includes DifxAppdriver component

2010-04-01 Thread Stephen Paterson
Thanks Phil, Sorry, when I said "the app" I meant the app and VC9 merge modules (i.e. 1+2+3 works, 1+2+4 works, 1+2+3+4 fails). There are no runtime dependencies, the installed sxs assembly is not used by any custom action. I'm currently testing on XP SP3. The error occurs in InstallF

Re: [WiX-users] Heat harvesting and fragment/component generation.

2010-04-01 Thread Brian Rogers
No, there isn't a way to do that. Gather all files at the folder level and putting them into a component can lead to many problems. What scenario do you have which requires this? Brian Rogers "Intelligence removes complexity." - Me http://blogs.msdn.com/icumove On Wed, Mar 31, 2010 at 4:33 AM,

Re: [WiX-users] MSI error 1935 (0x80070003) installing shared Win32 assembly - but only when installer includes DifxApp driver component

2010-04-01 Thread Wilson, Phil
VC 9.0 merge modules and SxS assemblies (VC 9.0 merge modules install in WinSxS too) are not available to custom action code on Vista and later because they're not really available until InstallFinalize and commit. You haven't said if there are run-time dependencies, and I don't know if the app

[WiX-users] MSI error 1935 (0x80070003) installing shared Win32 assembly - but only when installer includes DifxApp driver component

2010-04-01 Thread Stephen Paterson
I'm using WiX 3.0.5419.0 to generate an MSI that installs ... 1) an MFC app 2) the required VC9 merge modules 3) a Win32 shared SxS assembly 4) a DifxApp driver package. I can build an installer that will successfully install and uninstall the app and the drive

Re: [WiX-users] Error code:0xC00E5201 - Failed to create patch.

2010-04-01 Thread Wilson, Phil
I'm wondering if there's a parameter problem in there somewhere. You have a -PatchCreation parameter, and that -P is turning into the MsiMsp equivalent of -p and you're getting folders called \atchCreation and errors in there like -2147287037, which is 0x80030003 "The path %1 could not be found

Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get "Error 2836" in Repair mode

2010-04-01 Thread little.forest
Thanks Bob, You're right. They don't support MSI. From: Bob Arnson To: wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 5:22:35 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get "Error 2836" in Repair mode On 3/31/201

Re: [WiX-users] Conditions for Uninstall/Remove Only

2010-04-01 Thread little.forest
Thanks Sanjay. This is great. Especially there is a table - much clearer. From: Sanjay Rao To: General discussion for Windows Installer XML toolset. Sent: Wed, March 31, 2010 11:02:18 PM Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only try out

[WiX-users] Error code:0xC00E5201 - Failed to create patch.

2010-04-01 Thread Carolina Zuqueto Amaral
Hi, I used the example from this site (http://wix.sourceforge.net/manual-wix3/patch_building.htm) to create the patch. But when I generated the MSP the following error occurred: Failed to create patch. Error code: 0xC00E5201. How can I resolve it? Log: * Log starting: 2010-04-01 15:53:23

Re: [WiX-users] How to create web app/service on IIS 7 with WiX 3.0

2010-04-01 Thread Mike Carlson (DEV DIV)
If you schedule your deferred custom action after both ConfigureIIs and ConfigureIIs7, and it is deferred, then at the time it's run, it should be run after the websites are created. Note the log can be somewhat confusing at first when dealing with deferred custom actions because deferred custo

[WiX-users] AppSearch

2010-04-01 Thread Szentpali Janos
Hello, I created an MSI and transform for it that uses the AppSearch action. All the AppSearch related data (AppSearch, DrLocator, RegLocator and Signature tables) is in the transform. What I wanted to do is find a path in the registry and than check that a file exists in that path. So it was vita

Re: [WiX-users] MSI fails when compiled on a different machine

2010-04-01 Thread Kevin Garman
Sorry, I spoke too soon. We have different wix versions. On Thu, 2010-04-01 at 11:52 -0500, Kevin Garman wrote: > Hi, > > I've got a strange one today. When I compile our app/installer and run > the resulting msi everything works great. When a coworker compiles it > on his machine, the msi

[WiX-users] MSI fails when compiled on a different machine

2010-04-01 Thread Kevin Garman
Hi, I've got a strange one today. When I compile our app/installer and run the resulting msi everything works great. When a coworker compiles it on his machine, the msi he produces fails in my test environment--there doesn't seem to be any significant differences between our build environments.

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Wilson, Phil
What does this mean: "(e. g. it does not find the self-erased file)" in reference to the uninstall? If the only problem here is that you've installed a file, removed it, and now you want to prevent repair then make the Component guid null and you can remove it with impunity. Phil Wilson ---

Re: [WiX-users] Getting MSI Error 1613

2010-04-01 Thread Wilson, Phil
My first reaction would be to assume that the error message might actually be correct, and the MSI requires MSI version 4.5 or above. That's in the schema of your package (or page count in the MSI file summary info). Phil Wilson -Original Message- From: Sandeep Gautam (HCL Technologi

Re: [WiX-users] read a file + advertise

2010-04-01 Thread Castro, Edwin G. (Hillsboro)
Thinking out loud: I would probably use a RegistrySearch to set the properties in question from the registry. I think these execute prior to LaunchConditions and will leave the properties blank *if* the values _do not_ exist in the registry. I would then code a custom action that reads the xml

[WiX-users] First run notepad with my.cfg and only then start the service

2010-04-01 Thread Viv Coco
Hi all, I install along with my application: 1) a service that starts and stops my application as needed 2) a conf file that contains actually the user data and that will be shown to the user to modify as needed (I give the user the chance to change it by running notepad.exe with my conf file du

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread akash bhatia
if you need help about how to use the spawn dialog..then you have to look into my blog here . i have used the spawn dialog to populate the list of SQL servers on the network... On Thu, Apr 1, 2010 at 5:25 PM, akash bhatia <911ak...@gmail.com> wrote: > i was no

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread akash bhatia
i was not saying anythin about child dialog.. you custom dialog will be another andependent dialog... 1. lets say that you have a dialogA on click on next you are callin c# CA 2. no need to call any C# CA instead call another Dialog..say DialogB on NEXT of it (which is your custom dialog) wit

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Markus Karg
Thanks for the tip, but what we are seeking for is a "100% pure MSI" way. :-) > -Original Message- > From: Richard Horsley [mailto:richard.hors...@eicltd.com] > Sent: Donnerstag, 1. April 2010 12:57 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Prev

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley
If it needs to be independent and not part of an overall upgrade then no, msp is not the solution for you. Unfortunately im not entirely sure that there IS a way of doing what you want without there being a way of the user removing the msi using the control panel. The only other thing you could

[WiX-users] Crash in Votive project build

2010-04-01 Thread John Aldridge
I have a Votive(MSI) project in Visual Studio which sometimes crashes right at the end of the build with the traceback > Exception has been thrown by the target of an invocation. >at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] > arguments, SignatureStruct& sig, Metho

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Markus Karg
Well, the problem is actually less that we want to prevent *files* from getting removed (the module itself is not a file but a once-run proprietary script that removes itself as soon as it successfully terminated) but that we want to prevent (a) the uninstall button produces any kind of error messa

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread Sagar1111
Thanks for the reply akash. I tried your way. but it is not working. I am not able to navigate to next dialog on the click of a button in child Dialogbox. Sagar -- View this message in context: http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836192.html Sent from the wix-users

Re: [WiX-users] how to use heat to harvest VS projects

2010-04-01 Thread Neil Sleightholm
I will double check again but no I don't think they are. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Thu 01/04/2010 01:29 To: wix-users@lists.sourceforge.net Sub

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley
Theoretically yes, they will be able to remove the patch from "Programs and Features" if they click on "View installed updates", however, if you create the patch correctly, removing it will not actually remove the patched files. I have a patch process that works in this way. It should be noted t

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Markus Karg
Yes, but on modules no major updates will happen -- due to the technological solution, the major upgrade will replace the main product completele, including all modules. So the idea of having modules as .msp is actually fascinating us, as it would solve this issue, too. > -Original Message---

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Markus Karg
In theorey we could, but: Will this solve the problem? Will the user be able to see that the module was installed? > -Original Message- > From: Richard Horsley [mailto:richard.hors...@eicltd.com] > Sent: Donnerstag, 1. April 2010 11:42 > To: General discussion for Windows Installer XML t

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Rob Hamflett
Are you aware that disabling installs will prevent major upgrades? Rob On 01/04/2010 10:29, Markus Karg wrote: > We have to write a .msi to install modules into a preinstalled software. > > > > The problem is that once the module is installed, it can never get > uninstalled, as it modifies some s

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley
Could you create an .msp to patch the original installer to add these files? -Original Message- From: Markus Karg [mailto:k...@quipsy.de] Sent: 01 April 2010 10:30 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Prevent deinstallation We have to write a .msi

[WiX-users] CreateFolder, Permission, ignore errors

2010-04-01 Thread Alexander Gnauck
I have a setup where a folder is created and permissions should be set. Under some conditions this can fail but should abort the installation on failure. With File there is the vital flag, but I have found nothing similar for CreateFolder and Permissions. Is there a way to ignore errors and not

Re: [WiX-users] Getting MSI Error 1613

2010-04-01 Thread akash bhatia
have you validated your package using ORCA or MSIVal ? On Thu, Apr 1, 2010 at 2:37 PM, Sandeep Gautam (HCL Technologies Ltd) < v-sgo...@microsoft.com> wrote: > HI All, > > While doing installation I am getting error # 1613(This installation > package cannot be installed by the Windows Installer s

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread akash bhatia
for this you can set in the PROPERTY in your custom action. and create a custom dialog as per you requirements... on clicking the next of you current dialog... call C# CA first and then call this new customized dialog and set a condition as per the PROPERTY value. hope you ll reslove you i

Re: [WiX-users] WiX 3.0: Bug in LIGHT

2010-04-01 Thread Markus Karg
Thank you for posting the URL. Yes, we are suffering exactly from that bug, and the proposed solution is working. :-) BTW, I actually do not understand why the *unversioned* variant has to be *inside* the versioned one? I would understand if the semantics would be exchanged ("There shall be a r

[WiX-users] Prevent deinstallation

2010-04-01 Thread Markus Karg
We have to write a .msi to install modules into a preinstalled software. The problem is that once the module is installed, it can never get uninstalled, as it modifies some software-internal structures in a way that makes it impossible to undo. So, we have to prevent that somebody goes into

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread Sagar1111
the reason behind not using System.Windows.Forms is that i dont want my message box the appear behind mywizard. basically, What i want is a functionality like cancel button. I need to to popup a message from my custom action. Show it in front of the wizard. This pop-up dialog box would have t

Re: [WiX-users] How to create web app/service on IIS 7 with WiX 3.0

2010-04-01 Thread Igor Paniushkin
I think I still need one, I couldn't find these actions in standard IIS extension. Currently my custom actions is: 1) AspMaxRequestEntityAllowed and AspAllowSessionState on created website 2) Enable32bitAppOnWin64 (enables it) on application pools 3) Setting ManagedRuntimeVersion on created applica

[WiX-users] Getting MSI Error 1613

2010-04-01 Thread Sandeep Gautam (HCL Technologies Ltd)
HI All, While doing installation I am getting error # 1613(This installation package cannot be installed by the Windows Installer service. you must install a Windows service pack that contains a newer version of the Windows Installer service.). I am using Windows (r) Installer. V 4.00.6001.0.

Re: [WiX-users] CopyFile to be "executed" only on "first" install and removed only when a real uninstall

2010-04-01 Thread Viv Coco
btw, I could also do a normal component with a File Id, smth like: that means that template.ini would be on the target machine as aaa.ini and as bbb.ini which is fine. But how can I condition the bbb.ini component to be removed only on a real uninstall - not upgrades, repairs, modifies?

[WiX-users] CopyFile to be "executed" only on "first" install and removed only when a real uninstall

2010-04-01 Thread Viv Coco
Hi all, I install an aaa.ini file together with my binaries. I need a second ini file (bbb.ini) which is a copy of the first one, it just have a different name, and it's in the same directory. I was thinking about using the CopyFile but I need also the following: 1) the CopyFile, meaning the cr

Re: [WiX-users] WiX 3.0: Bug in LIGHT

2010-04-01 Thread Ondrej Zarevucky
Hi Markus, I had the same problem with one of our COM objects. I'm was told there problem in our COM object registration and I "fixed" it by moving the version independent class entry under the version dependent one using our custom built WiX post processing tool: More about this issue can

Re: [WiX-users] stop the service before uninstall

2010-04-01 Thread Viv Coco
Hi, Thanks for your answer. I was thinking also that maybe I could just somehow call an "external" CA _before_ InstallValidate that will take care to just stop the service. This way the service will be stopped, it will stop the app and when the InstallValidate comes into action everything is a

Re: [WiX-users] WiX 3.5: Error in HEAT

2010-04-01 Thread Markus Karg
WiX is release 3.0 Your proposal does not work, see here: C:\>SET PATH=%PATH%;"C:\Programme\Windows Installer XML v3\bin" C:\>HEAT file EXCEL8.OLB -gg -out EXCEL8.wxs Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5419.0 Copyright (C) Microsoft Corporation. All rights reserved