Re: [WiX-users] powershell is faling at Add-PSSnapin Microsoft.SharePoint.PowerShell is failing.
First, if the execution policy doesn't already allow the execution of scripts,
your Set-ExecutionPolicy will never be executed. You can't execute a script to
allow the execution of scripts.
Are you running into a 32/64 bit issue? The Microsoft.SharePoint.PowerShell
snap-in is only registered for 64bit PowerShell and I believe that the VBScript
CA will be running in a 32 bit environment which will get you 32 bit PowerShell.
-Original Message-
From: MYFLEX [mailto:shrinuen...@gmail.com]
Sent: Tuesday, August 31, 2010 4:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] powershell is faling at Add-PSSnapin
Microsoft.SharePoint.PowerShell is failing.
Hi all,
Please try to understand the problem and give some solution.
I am executing the powershell exe as vbscript CA as follows.
Function f1()
MsgBox(exe started)
Set objShell = CreateObject(Wscript.Shell)
vPSscrIpt = powershell.exe -NoExit c:\yyy\aa.ps1
objShell.Run vPSscrIpt
End Function
aa.ps1 content:
Set-ExecutionPolicy RemoteSigned
$ver = $host | select version
if ($ver.Version.Major -gt 1) {$Host.Runspace.ThreadOptions =
ReuseThread}
if ((Get-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction
SilentlyContinue) -eq $null) {
Add-PSSnapin Microsoft.SharePoint.PowerShell
}
#Add-PsSnapin Microsoft.SharePoint.PowerShell
Set-location $home
$sapp = Get-SPEnterpriseSearchServiceApplication –Identity “Search
Service
Application”
New-SPEnterpriseSearchCrawlContentSource –SearchApplication $sapp –Name
“c1”
–Type Custom –StartAddress protocol://servername –CrawlPriority Normal
–MaxPageEnumerationDepth 1 –MaxSiteEnumerationDepth 1
I decalred the Custom action as follows.
CustomAction Id=f1 BinaryKey=ca VBScriptCall=f1
Execute=deferred
Impersonate=no /
Executing the custom action in installExecute seq as follows.
Custom Action=f1 Before=ProcessComponents1/Custom
But this custom action is not able to registering the sharepoint snapin
to
the powershell. Add-PSSnapin Microsoft.SharePoint.PowerShell is
failing.
but If I run the vbscript manually it is executing successfully.
Please tell me some suggestion ...
--
View this message in context: http://windows-installer-xml-wix-
toolset.687559.n2.nabble.com/powershell-is-faling-at-Add-PSSnapin-
Microsoft-SharePoint-PowerShell-is-failing-tp5481703p5481703.html
Sent from the wix-users mailing list archive at Nabble.com.
---
---
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install .Net Framework 4
. --- --- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Thanks John for reply. 1. I tried John's solution, it builds fine, but when I install it fails Setup ended prematurely because of an error. Does John or anyone else know why? 2. If I use BootstrapperPackage for 4.0, like this: BootstrapperPackage Include=.NETFramework,Version=v4.0 how can I specify 4.0 Client, neither BootstrapperPackage Include=.NETFramework.Client,Version=v4.0 nor BootstrapperPackage Include=.NETFramework,Version=v4.0 Client is working. 3. Does anyone know where I can find out the property values for different .NetFramework versions? For example, in BootstrapperFile Include=Microsoft.Net.Framework.4.0 We use Microsoft.Net.Framework.4.0 for 4.0 and Microsoft.Net.Client.3.5 for 3.5 Client, when I use Microsoft.Net.Client.4.0, it gives me warning MSB3155: Item 'Microsoft.Net.Client.4.0' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\' I wonder there must be a place I can find out the standard value for each version, can someone help? Thanks. -Original Message- From: John Vottero [mailto:jvott...@mvpsi.com] Sent: June 16, 2010 5:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install .Net Framework 4 This works for me: ItemGroup BootstrapperPackage Include=.NETFramework,Version=v4.0 VisibleTrue/Visible ProductName.NET Framework 4.0/ProductName InstallTrue/Install /BootstrapperPackage /ItemGroup -Original Message- From: Jason Ding [mailto:jas...@geo-slope.com] Sent: Wednesday, June 16, 2010 6:51 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Install .Net Framework 4 I am tring to use Bootstrapper to install .Net Framework 4.0 by using a sample from this site: http://wix.sourceforge.net/manual-wix3/install_dotnet.htm I got a message like this: warning MSB3155: Item 'Microsoft.Net.Framework.4.0' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ Under the folder Bootstrapper/Packages, I have DotNetFX40 and DotNetFX40Client sub-folders. I am wondering if Microsoft.Net.Framework.4.0 is the correct BootstrapperFile name to use? Does anyone know where I can find the name for each .Net Framework Fix, like Microsoft.Net.Framework.3.5 for .Net Framework 3.5 ? Here is the code I am using, looks good to me unless the name in BootstrapperFile Include is wrong. Thanks for help. ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.4.0 ProductName.NET Framework 4/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Windows.Installer.4.5 ProductNameWindows Installer 4.5/ProductName /BootstrapperFile /ItemGroup ... --- --- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- --- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- --- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- --- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] Install .Net Framework 4
This works for me: ItemGroup BootstrapperPackage Include=.NETFramework,Version=v4.0 VisibleTrue/Visible ProductName.NET Framework 4.0/ProductName InstallTrue/Install /BootstrapperPackage /ItemGroup -Original Message- From: Jason Ding [mailto:jas...@geo-slope.com] Sent: Wednesday, June 16, 2010 6:51 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Install .Net Framework 4 I am tring to use Bootstrapper to install .Net Framework 4.0 by using a sample from this site: http://wix.sourceforge.net/manual-wix3/install_dotnet.htm I got a message like this: warning MSB3155: Item 'Microsoft.Net.Framework.4.0' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ Under the folder Bootstrapper/Packages, I have DotNetFX40 and DotNetFX40Client sub-folders. I am wondering if Microsoft.Net.Framework.4.0 is the correct BootstrapperFile name to use? Does anyone know where I can find the name for each .Net Framework Fix, like Microsoft.Net.Framework.3.5 for .Net Framework 3.5 ? Here is the code I am using, looks good to me unless the name in BootstrapperFile Include is wrong. Thanks for help. ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.4.0 ProductName.NET Framework 4/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Windows.Installer.4.5 ProductNameWindows Installer 4.5/ProductName /BootstrapperFile /ItemGroup ... -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiXNetFxExtension conditions
There is no guarantee that your product would work just fine with CLR 4.0 just because it works with CLR 2.0 (Framework 3.5). The WiX version test is a guarantee that it WON'T work because it will refuse to install. We work very hard to make sure that our software is upwardly compatible and the .NET Framework people do the same. All that hard work is negated if the installer has a pedantic version test. The test for a version of the Framework must (optionally) be Vx.x or any version that claims to support Vx.x. We write enterprise grade software. Enterprises don't want to upgrade without a good reason. Ten years from now, when a customer calls us up to ask if they can install a ten year old release on Windows 2020, I want to say yes. I don't want to explain that it won't work because the installer will refuse to install. For CLR 4.0 the CLR has moved into a SxS model whereby 4.0 can be loaded in-proc SxS 2.0 runtime, and the 5.0 runtime will be loaded into process alongside the 4.0 runtime, etc. Therefore, they are moving away from a model where CLR 4.0 assumes it can run CLR 2.0 runtime solutions with compatibility. There is extra work you will have to do with manifests to allow that scenario to work, and you will have to update that manifest for each new FW released. Your setup would also have to change to take this into account. The SxS model only works for applications. Libraries are still loaded into whatever version is loading them. I think you can also create a manifest that says run on whatever is installed (I haven't tried that). So actually it's a good thing that the 3.5 detection logic doesn't assume 4.0 matches because if it did you may find your solution installed onto a platform that is not back compat with your solution. No, it's actually a bad thing because it forces my software to break for no reason. Give me a chance to install so I can see if it works. John Vottero -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiXNetFxExtension conditions
Sorry, I didn't mean to give the impression of shooting the messenger. I just want to make sure that WiX doesn't turn won't guarantee it into guarantee it won't. -Original Message- From: Bryan Reich [mailto:bryan.re...@microsoft.com] Sent: Monday, February 15, 2010 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiXNetFxExtension conditions Don't shoot the messanger John. I'm just passing along what I know about the current situation. Also note that with the 4.0 FW, the CLR changed the way is registers itself and where you have to look in the registry to determine the current version, which is why the preexisting detection logic would now fail. Assemblies are not FW agnostic, so they won't just load into whatever CLR you tell them to. They might, but the CLR has basically said they won't guarantee it. That doesn't mean they won't try to maintain compat whenever possible, but there is a disconnect between the 2.0 runtime and the 4.0 runtime with regards to how much compat they are guranteeing. -- Bryan From: John Vottero [jvott...@mvpsi.com] Sent: Monday, February 15, 2010 11:49 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiXNetFxExtension conditions There is no guarantee that your product would work just fine with CLR 4.0 just because it works with CLR 2.0 (Framework 3.5). The WiX version test is a guarantee that it WON'T work because it will refuse to install. We work very hard to make sure that our software is upwardly compatible and the .NET Framework people do the same. All that hard work is negated if the installer has a pedantic version test. The test for a version of the Framework must (optionally) be Vx.x or any version that claims to support Vx.x. We write enterprise grade software. Enterprises don't want to upgrade without a good reason. Ten years from now, when a customer calls us up to ask if they can install a ten year old release on Windows 2020, I want to say yes. I don't want to explain that it won't work because the installer will refuse to install. For CLR 4.0 the CLR has moved into a SxS model whereby 4.0 can be loaded in-proc SxS 2.0 runtime, and the 5.0 runtime will be loaded into process alongside the 4.0 runtime, etc. Therefore, they are moving away from a model where CLR 4.0 assumes it can run CLR 2.0 runtime solutions with compatibility. There is extra work you will have to do with manifests to allow that scenario to work, and you will have to update that manifest for each new FW released. Your setup would also have to change to take this into account. The SxS model only works for applications. Libraries are still loaded into whatever version is loading them. I think you can also create a manifest that says run on whatever is installed (I haven't tried that). So actually it's a good thing that the 3.5 detection logic doesn't assume 4.0 matches because if it did you may find your solution installed onto a platform that is not back compat with your solution. No, it's actually a bad thing because it forces my software to break for no reason. Give me a chance to install so I can see if it works. John Vottero --- --- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- --- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] NativeImage Priority=0 does not work
When specifying Priority=0 on the NativeImage extension, the installation properly executes an ngen command with no /queue qualifier and the native image is successfully generated but, at the end of the install the NativeImage extension executes an ngen update /queue command which deletes all of the native images and queues an update. The result is that native images are not available when the installation is complete. This is WiX V3.0.5405. The following is a fragment of the ngen.log file which shows the JAMSScheduler.exe image being generated and showing that it is missing at the end of the installation. I added comments enclosed in []. 11/25/2009 18:32:43 [3560]: Command line: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe install C:\Program Files\MVPSI\JAMS\Scheduler\JAMSScheduler.exe 11/25/2009 18:32:43 [3560]: Installing assembly C:\Program Files\MVPSI\JAMS\Scheduler\JAMSScheduler.exe 11/25/2009 18:32:44 [3560]: Compiling assembly C:\Program Files\MVPSI\JAMS\Scheduler\JAMSScheduler.exe ... [other images from the installation are compiled] 11/25/2009 18:33:09 [3020]: Command line: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe install C:\Program Files\MVPSI\JAMS\Agent\JAMSHost32.exe 11/25/2009 18:33:09 [3020]: Installing assembly C:\Program Files\MVPSI\JAMS\Agent\JAMSHost32.exe 11/25/2009 18:33:10 [3020]: All compilation targets are up to date. 11/25/2009 18:33:10 [3020]: ngen returning 0x 11/25/2009 18:33:10 [3704]: Command line: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe update /queue 11/25/2009 18:33:10 [3704]: ngen returning 0x [That's the end of the NGEN commands executed by the MSI] [The following commands were entered by me to figure out what is going wrong] 11/25/2009 18:34:16 [2712]: Command line: ngen queue status 11/25/2009 18:34:16 [2712]: ngen returning 0x 11/25/2009 18:34:31 [804]: Command line: ngen display jamsscheduler 11/25/2009 18:34:31 [804]: Error: The specified assembly is not installed. 11/25/2009 18:34:31 [804]: ngen returning 0x 11/25/2009 18:34:37 [3768]: Command line: ngen display jamsshr 11/25/2009 18:34:37 [3768]: Error: The specified assembly is not installed. 11/25/2009 18:34:37 [3768]: ngen returning 0x [And some commands I entered later to verify that an update does delete everything] 11/30/2009 13:03:15 [10728]: Command line: ngen display jamswin 11/30/2009 13:03:15 [10728]: NGEN Roots: 11/30/2009 13:03:15 [10728]: C:\Program Files\MVPSI\JAMS\Client\JAMSWin.exe 11/30/2009 13:03:15 [10728]: NGEN Roots that depend on jamswin: 11/30/2009 13:03:15 [10728]: C:\Program Files\MVPSI\JAMS\Client\JAMSWin.exe 11/30/2009 13:03:15 [10728]: Native Images: 11/30/2009 13:03:15 [10728]: JAMSWin, Version=4.8.83.0, Culture=neutral, PublicKeyToken=7da961def3057cf2 11/30/2009 13:03:15 [10728]: ngen returning 0x 11/30/2009 13:04:46 [10936]: Command line: ngen update /queue 11/30/2009 13:04:47 [10936]: ngen returning 0x 11/30/2009 13:04:52 [10984]: Command line: ngen display jamswin 11/30/2009 13:04:52 [10984]: Error: The specified assembly is not installed. 11/30/2009 13:04:52 [10984]: ngen returning 0x -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] NetFxScheduleNativeImage and logging
I've been trying to figure out a problem with NetFxScheduleNativeImage in WiX V2.0.4820. I've been looking at the source code and I thought that all of the ExitOnFailure(hr, Some error message) calls were just dropping the error message. I got that idea from looking at dutil.h which defines ExitTrace to be nothing. Now, I just realized that wcautil.h overrides that so that ExitTrace calls WcaLogError. Could someone confirm that if NetFxScheduleImage in WiX v2.0.4820 hits a line like: ExitOnFailure(hr, failed to schedule NetFxExecuteNativeImageInstall action); and, hr contains an error, the message *should* be written to the msi log, right? Since I'm not seeing any of messages in the log, I'm looking for a code path that fails without calling ExitOnFailure, right? I've compared much of the relevant code in v2.0.4820, v2.0.5805 and v3.0.4721 and I don't see any significant differences so, if it should log something in v3.0.4721, I think it should log it in v2.0.4820. I have the code path in SchedNetFx narrowed down to the area between the end of the loop and the call to WcaFinalize and in that space, two MSI Record handles are created and closed. That could be the call to WcaProgressMessage and a call to WcaLog but, I don't get a message in the log file. Thanks! - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] NetFxScheduleNativeImage and logging
Thanks for the confirmation. Our new plan is to figure out what's wrong (or different) with this particular server. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2008 5:47 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] NetFxScheduleNativeImage and logging Yes, all of the Exit macros should log. That's why verbose log files are so useful for us. We get almost a stack trace to the exact failure. At this point, I think you should switch to suspecting the Windows Installer on this machine. Is it possible that the ::MsiProcessMessage() is causing the whole thing to blow up? That does end up as a cross process call I believe so it could be something screwy on the machine that's causing the failure. -Original Message- From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2008 14:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] NetFxScheduleNativeImage and logging I've been trying to figure out a problem with NetFxScheduleNativeImage in WiX V2.0.4820. I've been looking at the source code and I thought that all of the ExitOnFailure(hr, Some error message) calls were just dropping the error message. I got that idea from looking at dutil.h which defines ExitTrace to be nothing. Now, I just realized that wcautil.h overrides that so that ExitTrace calls WcaLogError. Could someone confirm that if NetFxScheduleImage in WiX v2.0.4820 hits a line like: ExitOnFailure(hr, failed to schedule NetFxExecuteNativeImageInstall action); and, hr contains an error, the message *should* be written to the msi log, right? Since I'm not seeing any of messages in the log, I'm looking for a code path that fails without calling ExitOnFailure, right? I've compared much of the relevant code in v2.0.4820, v2.0.5805 and v3.0.4721 and I don't see any significant differences so, if it should log something in v3.0.4721, I think it should log it in v2.0.4820. I have the code path in SchedNetFx narrowed down to the area between the end of the loop and the call to WcaFinalize and in that space, two MSI Record handles are created and closed. That could be the call to WcaProgressMessage and a call to WcaLog but, I don't get a message in the log file. Thanks! --- -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage
-Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, November 29, 2008 11:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage John Vottero wrote: Is the Action start 16:35:47: NetFxScheduleNativeImage. log text the result of calling WcaProgressMessage? That would confirm that I'm reading my way through the source code correctly. I don't think so -- I think that's coming straight from MSI when it invokes the CA. See https://blogs.msdn.com/heaths/archive/2008/02/12/debugging-custom- actions-leaked-handles.aspx for a list of what the handle types are. I'd suggest using /L*vx! as your logging switches; the ! tells MSI to flush each log line as it's written, which might show the Action start message earlier, before the record-creation log lines. Thanks for the pointer to the explanation of the MSI handle types. They confirmed that I worked my way through the source code correctly. But, I still can't see a code path between the end of the NetFxNativeImage while loop and the call to WcaFinalize that would create and close two record MSI Handles (type 790531). A successful uninstall creates and closes one record handle, in the call to WcaProgressMessage. The failing uninstall creates and closes two and I can't see how. I think that one is the call to WcaProgressMessage but I can't figure out where the other one could be coming from. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage
I used the Creating MSIHANDLE and Closing MSIHANDLE log messages to work my way through the source code for SchedNetFx. The MSI handles all seem to make sense, from the log I can see that it is reading two records from the NetFxNativeImage table and that's what I have in the table. In the log fragments that follow, I've made some notes after some of the log lines. My notes begin with -- and they usually indicate where in the source code the handle is being created or closed. A successful uninstall looks like this: MSI (s) (54!EC) [16:35:48:371]: Closing MSIHANDLE (42) of type 790531 for thread 1516 -- WcaFetchRecord (end of loop) MSI (s) (54!EC) [16:35:48:371]: Creating MSIHANDLE (49) of type 790531 for thread 1516-- WcaProgressMessage Action start 16:35:47: NetFxScheduleNativeImage. MSI (s) (54!EC) [16:35:48:521]: Closing MSIHANDLE (49) of type 790531 for thread 1516 -- WcaProgessMessage MSI (s) (54!EC) [16:35:48:521]: PROPERTY CHANGE: Adding NetFxExecuteNativeImageUninstall property. Its value is 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall C:\Program Files\MVPSI\JAMS\Client\JAMSWin.exe500C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall C:\Program Files\MVPSI\JAMS\Client\JAMS.exe500C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe update /queue500'. MSI (s) (54!EC) [16:35:48:521]: PROPERTY CHANGE: Adding NetFxExecuteNativeImageCommitUninstall property. Its value is 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall C:\Program Files\MVPSI\JAMS\Client\JAMSWin.exe500C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall C:\Program Files\MVPSI\JAMS\Client\JAMS.exe500C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe update /queue500'. MSI (s) (54!EC) [16:35:48:531]: Closing MSIHANDLE (33) of type 790541 for thread 1516 -- WcaFinalize A failed uninstall looks like this: MSI (s) (A0!10) [09:26:01:983]: Closing MSIHANDLE (11) of type 790531 for thread 7184 -- WcaFetchRecord (end of loop) MSI (s) (A0!10) [09:26:01:983]: Creating MSIHANDLE (18) of type 790531 for thread 7184-- WcaProgressMessage??? MSI (s) (A0!10) [09:26:01:983]: Closing MSIHANDLE (18) of type 790531 for thread 7184 -- WcaProgressMessage??? MSI (s) (A0!10) [09:26:01:983]: Creating MSIHANDLE (19) of type 790531 for thread 7184 MSI (s) (A0!10) [09:26:01:983]: Closing MSIHANDLE (19) of type 790531 for thread 7184 MSI (s) (A0!10) [09:26:01:983]: Closing MSIHANDLE (2) of type 790541 for thread 7184 -- WcaFinalize In the successful uninstall, WcaProgressMessage creates an MSIHANDLE, writes the Action start... progress message, closes the MSIHANDLE, sets two properties and then calls WcaFinalize. In the failed uninstall, there are two MSIHANDLES created and closed between the end of the NetFxNativeImage loop and the call to WcaFinalize but, can't see how that happens in the source code. One create/close could be a failed call of WcaProgressMessage but, I can't figure out where the second set comes from. My questions are: Is the Action start 16:35:47: NetFxScheduleNativeImage. log text the result of calling WcaProgressMessage? That would confirm that I'm reading my way through the source code correctly. What situations can cause WcaProgressMessage to fail? Has anyone seen it fail before? Thanks, John Vottero -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 5:27 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage Well, neither of those things make sense to me but it all sounds very suspicious. I'm not really sure what to suggest at this point but to look for badness on the client machine. GAC gone crazy? -Original Message- From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 13:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage This is kinda' strange looking: MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommands; Installed: Local; Request: Absent; Action: Null MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsSupport; Installed: Local; Request: Absent; Action: Null MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsFormats; Installed: Local; Request: Absent; Action: Null MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsTypes; Installed: Local; Request: Absent; Action: Null MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsHelp; Installed: Local; Request: Absent; Action: Null The problem is that you're trying to uninstall these Components (there are a few more) but something is telling the Windows Installer to ignore that. Do you have a Condition on those Components causing them to get stuck on the machine? This could be the cause of the problem
[WiX-users] Uninstall fails when calling NetFxScheduleNativeImage
I've been trying to figure out a problem with an upgrade failing when
calling the NetFxScheduleNativeImage CA. The failure occurs only on one
server (at a client site). We've narrowed the problem a little, the
failure happens during the uninstall, we can't even uninstall the
product. I'm including a verbose log of a failed uninstall, I hope
someone can see what's going wrong.
As a general question, how do you deal with problems like this? Is
there a way to tell msiexec to continue after errors? Is the Windows
Installer Cleanup Utility my only option? I would hate to zap it with
the cleanup utility without every knowing what the root problem was.
This is WiX v2.0.4820
Any help would be appreciated.
Here's the uninstall log:
=== Verbose logging started: 11/26/2008 9:26:01 Build type: SHIP
UNICODE 3.01.4000.4042 Calling process: E:\WINDOWS\system32\MSIEXEC.EXE
===
MSI (c) (B0:80) [09:26:01:748]: Resetting cached policy values
MSI (c) (B0:80) [09:26:01:748]: Machine policy value 'Debug' is 0
MSI (c) (B0:80) [09:26:01:748]: *** RunEngine:
*** Product: {26277F5D-6ED3-48BA-8E3C-D096E7A32306}
*** Action:
*** CommandLine: **
MSI (c) (B0:80) [09:26:01:748]: Client-side and UI is none or basic:
Running entire install on the server.
MSI (c) (B0:80) [09:26:01:748]: Grabbed execution mutex.
MSI (c) (B0:80) [09:26:01:779]: Cloaking enabled.
MSI (c) (B0:80) [09:26:01:779]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (B0:80) [09:26:01:779]: Incrementing counter to disable
shutdown. Counter after increment: 0
MSI (s) (A0:AC) [09:26:01:795]: Grabbed execution mutex.
MSI (s) (A0:C8) [09:26:01:795]: Resetting cached policy values
MSI (s) (A0:C8) [09:26:01:795]: Machine policy value 'Debug' is 0
MSI (s) (A0:C8) [09:26:01:795]: *** RunEngine:
*** Product: {26277F5D-6ED3-48BA-8E3C-D096E7A32306}
*** Action:
*** CommandLine: **
MSI (s) (A0:C8) [09:26:01:795]: Machine policy value
'DisableUserInstalls' is 0
MSI (s) (A0:C8) [09:26:01:795]: Setting cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: End dialog not enabled
MSI (s) (A0:C8) [09:26:01:795]: Original package ==
C:\WINDOWS\Installer\2ae1ad69.msi
MSI (s) (A0:C8) [09:26:01:795]: Package we're running from ==
C:\WINDOWS\Installer\2ae1ad69.msi
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: APPCOMPAT: looking for appcompat
database entry with ProductCode
'{26277F5D-6ED3-48BA-8E3C-D096E7A32306}'.
MSI (s) (A0:C8) [09:26:01:795]: APPCOMPAT: no matching ProductCode found
in database.
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: MSCOREE not loaded loading copy from
system32
MSI (s) (A0:C8) [09:26:01:811]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:811]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:811]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:811]: Machine policy value 'DisablePatch' is 0
MSI (s) (A0:C8) [09:26:01:811]: Machine policy value
'AllowLockdownPatch' is 0
MSI (s) (A0:C8) [09:26:01:811]: Machine policy value
'DisableLUAPatching' is 0
MSI (s) (A0:C8) [09:26:01:811]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s)
Re: [WiX-users] Uninstall fails when callingNetFxScheduleNativeImage
This is kinda' strange looking:
MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommands; Installed:
Local; Request: Absent; Action: Null
MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsSupport;
Installed: Local; Request: Absent; Action: Null
MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsFormats;
Installed: Local; Request: Absent; Action: Null
MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsTypes;
Installed: Local; Request: Absent; Action: Null
MSI (s) (A0:C8) [09:26:01:858]: Component: JAMSCommandsHelp;
Installed:
Local; Request: Absent; Action: Null
The problem is that you're trying to uninstall these Components (there
are a few more) but something is telling the Windows Installer to
ignore that. Do you have a Condition on those Components causing them
to get stuck on the machine? This could be the cause of the problem
(if the NtFXSched action doesn't like NULL action Components).
Thanks for the pointer but, I don't think it's the answer to my problem.
Those strange looking components provide our PowerShell support and
there is a condition on them that prevents installation if PowerShell
isn't already installed. The strange thing is that the log line says
Installed: Local when they actually are not installed (because
PowerShell wasn't installed). The Action: Null makes sense because
no action is needed.
Also, NetFxSched can deal with Action: Null because I recreated this
situation on a test machine and the uninstall worked. I'm still trying
to figure out what's different about the customer's production machine
where the uninstall is failing.
-Original Message-
From: John Vottero [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 07:54
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Uninstall fails when calling
NetFxScheduleNativeImage
I've been trying to figure out a problem with an upgrade failing when
calling the NetFxScheduleNativeImage CA. The failure occurs only on
one
server (at a client site). We've narrowed the problem a little, the
failure happens during the uninstall, we can't even uninstall the
product. I'm including a verbose log of a failed uninstall, I hope
someone can see what's going wrong.
As a general question, how do you deal with problems like this? Is
there a way to tell msiexec to continue after errors? Is the Windows
Installer Cleanup Utility my only option? I would hate to zap it with
the cleanup utility without every knowing what the root problem was.
This is WiX v2.0.4820
Any help would be appreciated.
Here's the uninstall log:
=== Verbose logging started: 11/26/2008 9:26:01 Build type: SHIP
UNICODE 3.01.4000.4042 Calling process:
E:\WINDOWS\system32\MSIEXEC.EXE
===
MSI (c) (B0:80) [09:26:01:748]: Resetting cached policy values
MSI (c) (B0:80) [09:26:01:748]: Machine policy value 'Debug' is 0
MSI (c) (B0:80) [09:26:01:748]: *** RunEngine:
*** Product: {26277F5D-6ED3-48BA-8E3C-D096E7A32306}
*** Action:
*** CommandLine: **
MSI (c) (B0:80) [09:26:01:748]: Client-side and UI is none or basic:
Running entire install on the server.
MSI (c) (B0:80) [09:26:01:748]: Grabbed execution mutex.
MSI (c) (B0:80) [09:26:01:779]: Cloaking enabled.
MSI (c) (B0:80) [09:26:01:779]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (B0:80) [09:26:01:779]: Incrementing counter to disable
shutdown. Counter after increment: 0
MSI (s) (A0:AC) [09:26:01:795]: Grabbed execution mutex.
MSI (s) (A0:C8) [09:26:01:795]: Resetting cached policy values
MSI (s) (A0:C8) [09:26:01:795]: Machine policy value 'Debug' is 0
MSI (s) (A0:C8) [09:26:01:795]: *** RunEngine:
*** Product: {26277F5D-6ED3-48BA-8E3C-D096E7A32306}
*** Action:
*** CommandLine: **
MSI (s) (A0:C8) [09:26:01:795]: Machine policy value
'DisableUserInstalls' is 0
MSI (s) (A0:C8) [09:26:01:795]: Setting cached product context:
machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: Using cached product context: machine
assigned for product: D5F772623DE6AB84E8C30D697E3A3260
MSI (s) (A0:C8) [09:26:01:795]: End dialog not enabled
MSI (s) (A0
Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 1:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install fails when calling
NetFxScheduleNativeImage
John Vottero wrote:
Yes, that's the first value 3 in the log file.
See http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/
for how to enable verbose logging. The NativeImage CAs log a fair bit
of
additional info.
I added LOGVERBOSE=1 to the msiexec command line but, I get the same
output.
The log shows LOGVERBOSE being set:
MSI (c) (50:D8) [10:51:37:047]: PROPERTY CHANGE: Adding LOGVERBOSE
property. Its value is '1'.
but, NetFxScheduleNativeImage still fails like this:
MSI (s) (70:B4) [10:51:37:734]: BeginTransaction: Locking Server
MSI (s) (70:B4) [10:51:37:734]: Machine policy value
'LimitSystemRestoreCheckpointing' is 0
MSI (s) (70:B4) [10:51:37:734]: SRSetRestorePoint skipped for this
transaction.
MSI (s) (70:B4) [10:51:37:734]: Server not locked: locking for product
{D074B9EC-D7F4-4116-B747-D1C7BDFF94AF}
MSI (s) (70:B4) [10:51:37:828]: Doing action: RemoveExistingProducts
MSI (s) (70:B4) [10:51:37:828]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:828]: Skipping RemoveExistingProducts action:
current configuration is maintenance mode or an uninstall
MSI (s) (70:B4) [10:51:37:828]: Doing action: ProcessComponents
MSI (s) (70:B4) [10:51:37:828]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:828]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:828]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:828]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: MsiUnpublishAssemblies
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: UnpublishFeatures
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: StopServices
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: DeleteServices
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: RemoveFiles
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:B4) [10:51:37:844]: Doing action: NetFxScheduleNativeImage
MSI (s) (70:B4) [10:51:37:844]: Note: 1: 2205 2: 3: ActionText
MSI (s) (70:C0) [10:51:37:844]: Invoking remote custom action. DLL:
E:\WINDOWS\Installer\MSI97A6.tmp, Entrypoint: SchedNetFx
MSI (s) (70:50) [10:51:37:859]: Generating random cookie.
MSI (s) (70:50) [10:51:37:875]: Created Custom Action Server with PID
8344 (0x2098).
MSI (s) (70:C0) [10:51:38:015]: Running as a service.
MSI (s) (70:C0) [10:51:38:031]: Hello, I'm your 32bit Impersonated
custom action server.
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70!3C) [10:51:38:062]: Note: 1: 2715 2:
MSI (s) (70:B4) [10:51:38:078]: Machine policy value 'DisableRollback'
is 0
MSI (s) (70:B4) [10:51:38:078]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\R
ollback\Scripts 3: 2
MSI (s) (70:B4) [10:51:38:078]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\R
ollback\Scripts 3: 2
MSI (s) (70:B4) [10:51:38:078]: No System Restore sequence number for
this installation.
MSI (s) (70:B4) [10:51:38:078]: Unlocking Server
MSI (s) (70:B4) [10:51:38:094]: MainEngineThread is returning 1603
MSI (s) (70:A0) [10:51:38:203]: Destroying RemoteAPI object.
MSI (s) (70:50) [10:51:38:203]: Custom Action Manager thread ending.
MSI (c) (50:D8) [10:51:38:203]: Back from server. Return value: 1603
MSI (c) (50:D8) [10:51:38:203]: Decrementing counter to disable
shutdown. If counter = 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (50:D8) [10:51:38:203]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
property. Its current value is '1'.
Action ended 10:51:38: ExecuteAction. Return value 3.
MSI (c) (50:D8) [10:51:38:203]: Doing action: FatalError
MSI (c) (50:D8) [10:51:38:203]: Note: 1: 2205 2: 3: ActionText
Action 10:51:38: FatalError.
Action start 10:51:38: FatalError.
MSI (c) (50:D8) [10:51:38:203]: Note: 1: 2205 2: 3: Error
MSI (c) (50:D8) [10:51:38:203]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2726
DEBUG: Error 2726: Action not found: FatalError
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2726. The arguments are: FatalError, ,
Action ended 10:51:38: FatalError. Return value 0.
Action ended 10:51:38: INSTALL. Return value 3
[WiX-users] Install fails when calling NetFxScheduleNativeImage
The following is a portion of an MSI log that I believe shows the problem. I could be wrong about that, reading MSI logs isn't the easiest thing in the world. The way I read this, it's removing files and then calls the NetFxScheduleNativeImage. Is that called when an assembly is being removed? This is a minor upgrade, nothing is being removed, assemblies are being replaced. It also seems that this error is only occurring on one specific machine. Can anyone give me some hints? Is the problem in NetFxScheduleNativeImage? Do you have any idea why this would work on hundreds of machines but fail on 1? This is WiX version 2.0.4820 Thanks, John Vottero MSI (s) (E8:04) [11:49:30:054]: Doing action: RemoveFiles MSI (s) (E8:04) [11:49:30:054]: Note: 1: 2205 2: 3: ActionText MSI (s) (E8:04) [11:49:30:054]: Doing action: NetFxScheduleNativeImage MSI (s) (E8:04) [11:49:30:054]: Note: 1: 2205 2: 3: ActionText MSI (s) (E8:3C) [11:49:30:054]: Invoking remote custom action. DLL: E:\WINDOWS\Installer\MSI9C58.tmp, Entrypoint: SchedNetFx MSI (s) (E8:44) [11:49:30:054]: Generating random cookie. MSI (s) (E8:44) [11:49:30:069]: Created Custom Action Server with PID 4316 (0x10DC). MSI (s) (E8:50) [11:49:30:085]: Running as a service. MSI (s) (E8:50) [11:49:30:085]: Hello, I'm your 32bit Impersonated custom action server. MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8:04) [11:49:30:100]: Machine policy value 'DisableRollback' is 0 MSI (s) (E8:04) [11:49:30:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\R ollback\Scripts 3: 2 MSI (s) (E8:04) [11:49:30:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\R ollback\Scripts 3: 2 MSI (s) (E8:04) [11:49:30:100]: No System Restore sequence number for this installation. MSI (s) (E8:04) [11:49:30:100]: Unlocking Server MSI (s) (E8:04) [11:49:30:116]: MainEngineThread is returning 1603 MSI (s) (E8:F4) [11:49:30:225]: Destroying RemoteAPI object. MSI (s) (E8:44) [11:49:30:225]: Custom Action Manager thread ending. MSI (c) (28:D0) [11:49:30:225]: Back from server. Return value: 1603 MSI (c) (28:D0) [11:49:30:225]: Decrementing counter to disable shutdown. If counter = 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (28:D0) [11:49:30:225]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:49:30: ExecuteAction. Return value 3. MSI (c) (28:D0) [11:49:30:225]: Doing action: FatalError MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2205 2: 3: ActionText Action 11:49:30: FatalError. Action start 11:49:30: FatalError. MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2205 2: 3: Error MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2726 DEBUG: Error 2726: Action not found: FatalError The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2726. The arguments are: FatalError, , Action ended 11:49:30: FatalError. Return value 0. Action ended 11:49:30: INSTALL. Return value 3. - 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage
Yes, that's the first value 3 in the log file. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 10:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage Is that the first instance of value 3 in the log file? If not can you share that part of the log file. If so, it does appear that the SchedNetFx entry point failed. I don't know that code well and there is nothing useful in the log, unfortunately. -Original Message- From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 15:50 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Install fails when calling NetFxScheduleNativeImage The following is a portion of an MSI log that I believe shows the problem. I could be wrong about that, reading MSI logs isn't the easiest thing in the world. The way I read this, it's removing files and then calls the NetFxScheduleNativeImage. Is that called when an assembly is being removed? This is a minor upgrade, nothing is being removed, assemblies are being replaced. It also seems that this error is only occurring on one specific machine. Can anyone give me some hints? Is the problem in NetFxScheduleNativeImage? Do you have any idea why this would work on hundreds of machines but fail on 1? This is WiX version 2.0.4820 Thanks, John Vottero MSI (s) (E8:04) [11:49:30:054]: Doing action: RemoveFiles MSI (s) (E8:04) [11:49:30:054]: Note: 1: 2205 2: 3: ActionText MSI (s) (E8:04) [11:49:30:054]: Doing action: NetFxScheduleNativeImage MSI (s) (E8:04) [11:49:30:054]: Note: 1: 2205 2: 3: ActionText MSI (s) (E8:3C) [11:49:30:054]: Invoking remote custom action. DLL: E:\WINDOWS\Installer\MSI9C58.tmp, Entrypoint: SchedNetFx MSI (s) (E8:44) [11:49:30:054]: Generating random cookie. MSI (s) (E8:44) [11:49:30:069]: Created Custom Action Server with PID 4316 (0x10DC). MSI (s) (E8:50) [11:49:30:085]: Running as a service. MSI (s) (E8:50) [11:49:30:085]: Hello, I'm your 32bit Impersonated custom action server. MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8!00) [11:49:30:100]: Note: 1: 2715 2: MSI (s) (E8:04) [11:49:30:100]: Machine policy value 'DisableRollback' is 0 MSI (s) (E8:04) [11:49:30:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\ R ollback\Scripts 3: 2 MSI (s) (E8:04) [11:49:30:100]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\ R ollback\Scripts 3: 2 MSI (s) (E8:04) [11:49:30:100]: No System Restore sequence number for this installation. MSI (s) (E8:04) [11:49:30:100]: Unlocking Server MSI (s) (E8:04) [11:49:30:116]: MainEngineThread is returning 1603 MSI (s) (E8:F4) [11:49:30:225]: Destroying RemoteAPI object. MSI (s) (E8:44) [11:49:30:225]: Custom Action Manager thread ending. MSI (c) (28:D0) [11:49:30:225]: Back from server. Return value: 1603 MSI (c) (28:D0) [11:49:30:225]: Decrementing counter to disable shutdown. If counter = 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (28:D0) [11:49:30:225]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:49:30: ExecuteAction. Return value 3. MSI (c) (28:D0) [11:49:30:225]: Doing action: FatalError MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2205 2: 3: ActionText Action 11:49:30: FatalError. Action start 11:49:30: FatalError. MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2205 2: 3: Error MSI (c) (28:D0) [11:49:30:225]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2726 DEBUG: Error 2726: Action not found: FatalError The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2726. The arguments are: FatalError, , Action ended 11:49:30: FatalError. Return value 0. Action ended 11:49:30: INSTALL. Return value 3. --- -- 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=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- -- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications
Re: [WiX-users] How to detect if .NET framework 2.0 or higher isinstalled
We check for a minimum version of mscoree.dll, like this: Property Id=MINFRAMEWORK DirectorySearch Id=MinFrameworkDir Depth=0 Path=[SystemFolder] FileSearch Id=MinFrameworkFile MinVersion=1.1.4322 Name=mscoree.dll / /DirectorySearch /Property Condition Message=.NET Framework 1.1 (or higher) is not present on the computer. ![CDATA[MINFRAMEWORK ]] /Condition -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Sunday, June 08, 2008 5:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to detect if .NET framework 2.0 or higher isinstalled Who knows what MS will do for 4.0, I don't think we can guess. .Net 3.0 and 3.5 are just marketing labels, they are really 2.0 plus service packs. I know that doesn't help but I don't see what we as install writers can do. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Sent: 08 June 2008 22:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to detect if .NET framework 2.0 or higher is installed While that is true for 3.0 and 3.5, that might not necessarily be true for 4.0. For example, if they have 2.0 they do not necessarily have 1.1 or 1.0, as they were both different CLR versions. The reason it is true for 3.0 and 3.5 is because they are library extensions and run on the same CLR version as 2.0. On Sun, Jun 8, 2008 at 1:57 PM, Neil Enns [EMAIL PROTECTED] wrote: Right. A user can't just install .NET 3.5 as the installer will automatically install .NET 2.0 and 3.0 as well. If your installer does a check for .NET 2.0 via the reg key (or using the NetFxExtension that comes with WiX), the check will pass if the user has only installed .NET 3.5 since the other two frameworks will automatically be there as well. Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ryan O'Neill [EMAIL PROTECTED] Sent: Sunday, June 08, 2008 11:51 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How to detect if .NET framework 2.0 or higher is installed I think that's what he said. It will detect .Net 2.0 or greater, so 2.0, 3.0, 3.5 and 4.x will be covered as any future .Net installation is backwards compatible and has the previous runtimes installed too. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ravit Shapira Sent: 08 June 2008 18:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to detect if .NET framework 2.0 or higher is installed I actually thought about your suggestion. The problem is that we will have to search the registry key of each version of .NET and I'm trying to find a general solution that will work for all versions of .NET 2.0 and higher, so that we will not have to change the setup code when .NET version 4.0 will release. Thanks, -Ravit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Sunday, June 08, 2008 6:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to detect if .NET framework 2.0 or higher is installed I think that key should be present if 3.5 is installed as the 3.5 install installs 2.0. If you are using WiX v3 you can also do something like this: PropertyRef Id=NETFRAMEWORK20/ Condition Message=.NET Framework 2.0 is not present on this computer. Installed OR NETFRAMEWORK35 /Condition Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ravit Shapira Sent: 08 June 2008 10:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to detect if .NET framework 2.0 or higher is installed Hi, I want to be able to detect if .NET framework 2.0 or higher is installed. I've found how I can look for the .NET framework 2.0 in wix: Property Id=NETFRAMEWORK20 RegistrySearch Id=NetFramework20 Root=HKLM Key=Software\Microsoft\NET Framework Setup\NDP\v2.0.50727 Name=Install Type=raw / /Property ConditionInstalled or NETFRAMEWORK20/Condition The problem with my current implementation is that it looks for the registry key of v2.0, while the setup that I create should run on .NET 2.0 or higher (3.5 for example). Thanks, Ravit
Re: [WiX-users] Embedding patch inside bootstrapper
Is there an easy way to create a setup.exe bootstrapper that embeds the msi/msp inside it? I can get msbuild to create the setup.exe just fine, but I need to distribute my patch as a single file. My googling has suggested this isn't a feature of msbuild and I've yet to find another tool to do this (that isn't a pain). We use IExpress.exe to do this. Open a CMD.EXE window and type IEXpress.exe. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing built MSIs?
MSBuild does come with a signing task, it's the SignFile task. You can sign your msi files with signtool.exe, MSBuild SignFile or PowerShell's Set-AuthenticodeSignature. I don't know why WiX should add another option. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, May 07, 2008 5:33 PM To: Neil Enns; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Signing built MSIs? Write a task that signs files? smile/ Seriously, some people have suggested that WiX should sign files. I'm a little skeptical because it doesn't seem like something the compiler/linker should be doing. Others have noted that signing is done by csc.exe to create strong named assemblies. I've argued that is a little different because the signatures are for different reasons... but it isn't a good argument. grin/ So, we've waffled on this a little bit. One thing I *do not* think WiX should be doing is signing all the installed files. That should be handled before you get to the binding process. However, I'm open to discussion... PS: Why doesn't MSBuild come with a signing task? shrug/ I want C++ tasks first in any case. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, May 07, 2008 13:36 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Signing built MSIs? Does WiX 3.0 currently have any support for signing the generated MSI at the end of the build process? I took a quick peek at the wix.targets file and didn't see anything obvious. Is there a recommended way of doing this? Thanks, Neil - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix mailing lists open to public = more spam
If anyone has any other opinions on this topic, please do make your voice heard. I'm still following this thread and trying to figure out if I should lock non-members out of the list. I'm still very hesitant to do that since it raises the bar for people just starting to get involved with WiX (and we don't need to make anything *harder* smile/). What will keep the spammers from joining the list? - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting Uninstall/.../InstallLocation in registry
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Carl Daniel
Sent: Tuesday, February 12, 2008 6:13 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting Uninstall/.../InstallLocation in registry
I'm sure this has been asked before, but as there doesn't seem to be a
workable search mechanism for the archives (that I could find!), I'll
ask at the risk of being redundant...
I have a WIX project, originally created by running dark.exe against
an
MSI produced by a VS deployment project. One of the many things I'm
trying to accomplish in the conversion to WIX is to address several
points that were raised during Vista logo compliance testing.
One of those compliance issues is that the MSI created by the
deployment
projects fails to set the InstallLocation value in the
HKLM/Software/Microsoft/Windows/CurrentVersion/Uninstall/{productID}
registry key. Unsurprisingly, the MSI generated from the dark-created
WIX file also fails to set that value.
So what's the recommended way of getting this key set? This is
something that I would have expected to be completely automatic, but
apparently my expectations are out of whack with reality.
All pointers appreciated!
Here's what we did to solve this problem:
CustomAction
Id=SAVETARGETDIR
Property=ARPINSTALLLOCATION
Value=[TARGETDIR] /
and then sequence it after InstallValidate
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Are the MSI built with WiX v2 is compatible with Vista/Server 2008?
I'm very new to WiX and have just subscribed to this mailing list. Sorry, if the questions below are stupid. Due to the fact that it is recommended to use WiX v2 for production projects so far, I have a couple of questions: 1) Will the MSI produced by WiX v2 be valid and compatible with Vista/Server 2008 requirements? I mean those defined in Certified For Windows Server 2008 program, for instance. 2) Does the MSI produced by WiX v2 validate against validation packages like Full MSI validation? Yes, WiX V2 can be used to create Certified For packages. We use WiX V2 and we are Certified for Vista. We haven't gotten certified for 2008 yet but, I don't anticipate a problem. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Services + Vista + GAC
Just mark your service as starting automaticly and you shouldn't have any problem. Then Windows will start the service when its needed. How does Windows know when the service needs to be started (other than boot time)? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Services + Vista + GAC
Another solution that was suggested here was to use a deferred custom action to start the service. But that also doesn't seem to work. Using WiX 2.x branch and it results in a runtime error. The custom action works OK if run outside of the MSI. The error returned is Unable to schedule operation. The action must be scheduled between InstallInitialize and InstallFinalize. Currently I have it as, Binary Id=blah SourceFile=/ CustomAction Id=blah_ca ExeCommand= BinaryKey=blah Execute=deferred Impersonate=no Return=ignore / InstallExecuteSequence Custom Action=blah_ca OnExit=success / /InstallExecuteSequence Any ideas? I could be wrong but, I think your problem is that you're trying to use a binary that's embedded in the msi and this is only available between InstallInitialize and InstallFinalize. After InstallFinalize, all the temporary bits of your msi have been cleaned up. To run a custom action as late as you need, it has to be something you install or something already on the system. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Monitoring progress of chained installs
Your requirements are similar to ours. We need to ask the user what features they want to install then, depending on their answers, they may need MSMQ and SQL Server. They can also choose not to install SQL Server because they want to use SQL server over the network. We also use IExpress to pack everything into a single executable. We use the MSBuild GenerateBootstrapper task to create an initial bootstrapper which checks for V2.0 of the .NET Framework and V3.1 of Windows Installer. We also created our own UI/Bootstrapper in C#. We set IExpress to run the MSBuild generated bootstrapper and then run our bootstrapper as the PostInstallCmd. It's much easier to do UI in straight C# than it is in WiX/Windows Installer. Our installer asks all the questions then executes whatever install commands are required (it never makes any direct changes to the system). Since our product requires the .NET Framework, we were comfortable writing the installer in C#. If your product doesn't require .NET you might not want to add that dependency just for the installer. Still, writing the installer in C++ might be easier than trying to do it in WiX. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim Sent: Monday, November 12, 2007 8:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Monitoring progress of chained installs I have a moderately complex application that I am trying to write an installer for. The current installer does not use Windows Installer at all, but I believe moving to Windows Installer would provide several benefits for our customer base. Our product requires services to be started, file shares to be created, and web sites added to the existing IIS instance. Fortunately, it looks like WiX can handle most of these requirements, and have learned a great deal about both WiX and the Windows Installer over the last few weeks. I have a few lingering questions, though. Our application has a number of prerequisites that must be present on the user's machine before our application can be installed. Additionally, we really don't know all of those prerequisites until after the user interview via the wizard is complete (e.g., since our application requires a database, the user may opt to install SQL Server Express instead of using an existing database server). The correct sequence of events during an install is as follows: * Interview the user to determine desired settings * Install prerequisites * Install product Some of the prerequisites are in IExpress self-extracting executables (like the .NET framework installer), some are standalone MSI files. Ideally, I would like to offer an integrated install experience, where the users sees the interview, then one progress dialog box for all of the subsequent prerequisite and application installs. Furthermore, I'd really like to let the user install using only the .msi and not have to use an external bootstrapper executable, but using current versions of Windows Installer, I know that's a pipe dream. After that long preamble, here are my questions. 1) Windows Installer has a fairly robust UI mechanism, and it seems smart to leverage that for the user interview. I'd really rather not implement the user interview in the chainer in C++ code (yes, I've done enough research to know I need a chainer), as that seems much harder to modify for future releases than WiX code. How can I pass the data collected in the interview to another install process? 2) I've been experimenting with using an external UI to monitor the install progress, but it seems that the MsiSetExternalUI API only works for products installed via MsiInstallProduct. How can I handle displaying progress for those Windows Installer packages embedded as part of IExpress installs? 3) I've looked at the Windows Installer 4.5 beta, which includes some facilities for embedding a chainer. Does this help me at all? Looking at these questions, it looks like most of them are not specifically WiX questions, but may be more generic Windows Installer questions. If anyone wants to redirect me to a forum for those questions, I'd be happy to raise them there. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Bootstrapper (install different drivers, acrobat reader)
I am able to use Visual Studio bootstrapper to install .NET other micosoft software. How can I modify it to install other exe files, such as sentinel.exe, AdobeReader.exe, I need to launch many different executables during my product install. This should help: http://www.codeplex.com/bmg - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix CA
This works for us: CustomAction Id=SetLoadDB Property=LoadDB Value=quot;[#JAMSDBAEXE]quot; LOAD/UI=[UILevel]/ CustomAction Id=LoadDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=..\ExternalReferences\wixca.dll/ InstallExecuteSequence Custom Action=SetLoadDB After=InstallFiles / Custom Action=LoadDB After=StartServices![CDATA[REMOVEALL]]/Custom /InstallExecuteSequence From: Harini Gurusamy [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 1:43 AM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix CA Still My catsign.exe is not executed. I tried (SourceFile=c:\windows\system32\catsign.exe ) also InstallExecuteSequence Custom Action='Launchfile' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence CustomAction Id =Launchfile Return=check FileKey=catsign.exe ExeCommand= / CustomAction Id=LaunchFile BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=catsign.exe/ From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Sunday, October 21, 2007 9:22 PM To: Harini Gurusamy; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix CA What's missing is: CustomAction Id=LaunchFile BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=..\ExternalReferences\wixca.dll/ And the scheduling of that CA. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harini Gurusamy Sent: Sunday, October 21, 2007 10:18 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix CA Thanks for the quick help.. I tried this approach of using FileKey and doesn't work. Do I need the second step even if I am using execommand ?? Whats missing here InstallExecuteSequence Custom Action='LaunchFile' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence CustomAction Id='LaunchFile' return='check' FileKey='foo.exe' ExeCommand='' / From: John Vottero [ma I ilto:[EMAIL PROTECTED] Sent: Sunday, October 21, 2007 7:03 PM To: Harini Gurusamy; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix CA It's a two step process, you have to set the property with the command you want to execute and then you have to execute the command. Your custom action sets the property. I'm not sure if the [SourceDir] reference will work or not, you can just use the file ID with a #, like this: CustomAction Id=SetLoadDB Property=LoadDB Value=quot;[#JAMSDBAEXE]quot; LOAD/UI=[UILevel]/ After that, you need to execute the command like this: CustomAction Id=LoadDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=..\ExternalReferences\wixca.dll/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harini Gurusamy Sent: Sunday, October 21, 2007 8:47 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix CA I am using WIX 2.0. I am trying to call an executable as part of my install. The EXE file is one of the installed files. But after the install , the EXE is never getting executed. Any pointers ?? My code snippet looks like InstallExecuteSequence Custom Action='LaunchFile
Re: [WiX-users] Wix CA
What's missing is: CustomAction Id=LaunchFile BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=..\ExternalReferences\wixca.dll/ And the scheduling of that CA. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harini Gurusamy Sent: Sunday, October 21, 2007 10:18 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix CA Thanks for the quick help.. I tried this approach of using FileKey and doesn't work. Do I need the second step even if I am using execommand ?? Whats missing here InstallExecuteSequence Custom Action='LaunchFile' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence CustomAction Id='LaunchFile' return='check' FileKey='foo.exe' ExeCommand='' / From: John Vottero [ma I ilto:[EMAIL PROTECTED] Sent: Sunday, October 21, 2007 7:03 PM To: Harini Gurusamy; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix CA It's a two step process, you have to set the property with the command you want to execute and then you have to execute the command. Your custom action sets the property. I'm not sure if the [SourceDir] reference will work or not, you can just use the file ID with a #, like this: CustomAction Id=SetLoadDB Property=LoadDB Value=quot;[#JAMSDBAEXE]quot; LOAD/UI=[UILevel]/ After that, you need to execute the command like this: CustomAction Id=LoadDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ Binary Id=wixca SourceFile=..\ExternalReferences\wixca.dll/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harini Gurusamy Sent: Sunday, October 21, 2007 8:47 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix CA I am using WIX 2.0. I am trying to call an executable as part of my install. The EXE file is one of the installed files. But after the install , the EXE is never getting executed. Any pointers ?? My code snippet looks like InstallExecuteSequence Custom Action='LaunchFile' After='InstallFiles'NOT Installed/Custom /InstallExecuteSequence CustomAction Id =LaunchFile Property=QtExecCmdLine Value='[Sourcedir]foo.exe' Return=check / **I tried InstallFinalize , still doesn't work Thanks Harini - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)
Is that all the diagnostic output? The Initial Properties section seems to be missing. Did you move or copy the MSBuild.exe executable? If so, don't. It looks for other files (like *.task) in the same location as the executable. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of hina1703 Sent: Friday, October 19, 2007 9:54 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide) Here is the diagnostic output: Initial Items: BootstrapperFile Microsoft.JSharp.2.0 Microsoft.Net.Framework.2.0 Microsoft.Sql.Server.Express.1.0 Microsoft.Windows.Installer.3.1 Target Bootstrapper in file C:\WIX\Test_Dot_NET\Bootstrapper.xml: MSBUILD : warning MSB4010: The *.tasks files could not be successfully loade d from their expected location C:\WIX\Test_Dot_NET. Default tasks will not be available. C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The GenerateBootst rapper task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is public and implements the Microsoft.Build.Framework.ITask interface. 3.) The ta sk is correctly declared with UsingTask in the project file, or in the *.tasks files located in the C:\WIX\Test_Dot_NET directory. Done building target Bootstrapper in project Bootstrapper.xml -- FAILED. Done building project Bootstrapper.xml -- FAILED. Project Performance Summary: 94 ms C:\WIX\Test_Dot_NET\Bootstrapper.xml 1 calls Target Performance Summary: 47 ms Bootstrapper 1 calls Build FAILED. MSBUILD : warning MSB4010: The *.tasks files could not be successfully loaded from their expected location C:\WIX\Test_Dot_NET. Default tasks will not be av ailable. C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The GenerateBootstra pper task was not found. Check the following: 1.) The name of the task in the p roject file is the same as the name of the task class. 2.) The task class is pu blic and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with UsingTask in the project file, or in the *.tasks f iles located in the C:\WIX\Test_Dot_NET directory. 1 Warning(s) 1 Error(s) I don't have any *.tasks file in the project directory. Do I need to create one? Thanks, Hina John Vottero wrote: Try adding /v:diag to your command to get diagnostic output and post that. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of hina1703 Sent: Thursday, October 18, 2007 5:27 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide) Thanks for your reply John. I tried to build bootstrapper by doing msbuild bootstrapper.xml, but I am getting error: error MSB4036: The GenerateBootstrapper task was not found. My bootstrapper.xml looks as below: ?xml version=1.0 encoding=UTF-8? Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductName.NET Framework 2.0/ProductName /BootstrapperFile BootstrapperFile Include= Microsoft.Windows.Installer.3.1 ProductNameWindows Installer 3.1/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.JSharp.2.0 ProductNameVisual J# redistributable/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0 ProductNameSQL Server 2005 Express Edition/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=Test_Dot_NET.msi ApplicationName=Test_Dot_NET BootstrapperItems=@(BootstrapperFile) OutputPath=bin ComponentsLocation=Relative Culture=pt-PT Path=C:\WIX\Test_Dot_NET\release / /Target /Project Please advise. Hina John Vottero wrote: You don't include the bootstrapper xml in the WiX file. You build your app.msi from the WiX file. Then you build your bootstrapper by doing: msbuild bootstrapper_project_file.xml -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of hina1703 Sent: Tuesday, October 16, 2007 12:48 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide) Please reply. Hina hina1703 wrote: Thanks for the reply. So will the bootstrapper file be .xml file? How can I include xml file into wxs file? Is there any good
Re: [WiX-users] How to keep guids in similar setups
If two components have the same GUID, they must be the same including the directory. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Ilya Slobodin Sent: Monday, October 15, 2007 2:29 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to keep guids in similar setups Hello List, I'm trying to build multiple similar setups (Pro, Standard, Base) of our product from a single WiX sources. And I'm trying to keep guids whenever possible. Bob Arnson wrote earlier in this list that guids are product-global and it's ok to keep the same guids, but when products are installed into different directories. Currently my investigations show most components are really product-global while some component types do not. Non-advertised shortcuts and CU registry keys are not uninstalled when another product that has the same components with the same guids is installed in different directory. E.g. we have two products, Pro and Base, both have My.exe with non-advertised shortcut pointing on it. Both exe files have the same guid and both shortcuts have the same (but different) guid. Program Files\My Product Pro\My.exe StartMenu\Programs\My Product Pro\My Product Shortcut.lnk HKCU\My Product Pro\ShortcutKeyPath Program Files\My Product Base\My.exe StartMenu\Programs\My Product Base\My Product Shortcut.lnk HKCU\My Product Base\ShortcutKeyPath 1. Install Pro into Program Files\My Product Pro 2. Install Base into Program Files\My Product Base 3. Uninstall Base (StartMenu\Programs\My Product Base\My Product Shortcut.lnk remains and it has Action: Null in the log) 4. Uninstall Pro (Pro\Shortcut to My.exe uninstalled) I use MSI 3.01 Could someone comment on this? Best regards, Ilya Slobodin --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Digitally signing packages
The wix schema seems to have support for digitally signing packages - the DigitalCertificate element, the DigitalCertificateRef element - but I can't see how they're meant to be used. Presumably light has to have access to the certificate's private key at some point, and it isn't clear to me from the docs how it gets this. It also isn't clear what format the certificate's SourceFile has to be in. I don't think that the DigitalCertificate element is used to sign MSIs, it's for installing certificates for web sites (I'm not sure since I don't use it). You sign your MSI after it's been created using either SIGNTOOL.EXE, PowerShell's Set-AuthenticodeSignature cmdlet or MSBuild's SignFile task. Is there a list somewhere of what CAs Microsoft trusts to issue code- signing certs? We're willing to pay the Verisign tax, but would be happier paying someone else for a cert as long as it is trusted identically... We bought ours from Thawte and haven't had any problems. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to configure SQL Express bootstrap
Find the Package.xml file for SQL Express, edit it and look for the Command PackageFile=sqlexpr32.exe Arguments=.. element. Change the Arguments to what you want. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse Sent: Tuesday, October 02, 2007 5:41 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to configure SQL Express bootstrap I created a bootstrapper with MSbuild to install SQL Express, but I'd like to change the configuration... Since it is in a bootstrap it doesn't show the install wizard. Surely configuring the database engine is possible. Does someone have an example or can please point me in the right direction? Thanks. Eric Latendresse Programmer Optimum Solutions, Inc. 615-329-2313x 2229 615-329-4448 fax [EMAIL PROTECTED] www.optimum-solutions.com http://www.optimum-solutions.com/ Your Only Payroll,HR and time attendance solution - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Spaces in Shortcut/@Arguments
I'm generating a number of shortcuts to programs/scripts/etc that take arguments. One tester has noticed that a shortcut set up like: Shortcut Id=SHORTCUT_logconf Directory=ProgramMenuDir Name=logconf LongName=Log Configuration Tool Target=[INSTALLDIR]bin\wish.exe Arguments=[INSTALLDIR]bin\logconfig WorkingDirectory=DATADIR/ fails because at install-time [INSTALLDIR] becomes C:\Program Files\Foo, and so the expected single argument gets split into C:\Program and Files\Foo\bin\logconfig. Should something be properly escaping/quoting the argument? I can slip a couple of quot;s into my arguments string, but that feels like a layering hack. WiX and MSI have no way of knowing that your argument is a path that needs to be quoted if it contains a space. You're going to have to add the quot;s. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Spaces in Shortcut/@Arguments
On Thursday, September 27, 2007, at 01:00PM, John Vottero [EMAIL PROTECTED] wrote: Should something be properly escaping/quoting the argument? I can slip a couple of quot;s into my arguments string, but that feels like a layering hack. WiX and MSI have no way of knowing that your argument is a path that needs to be quoted if it contains a space. You're going to have to add the quot;s. Surely the Installer knows it is replacing part of a string with a string containing a space? It feels like that's the code that should be doing the quoting, but you're probably right about me having to do it instead... There's no way for the installer to know if the string that you're building is supposed to be one argument (with quotes) or two arguments. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit packages
We're creating separate 64-bit and 32-bit packages, and so far my 64- bit packages are refusing to install in 2003 Server. The most interesting of the errors reported by Orca is: ICE80ERRORThis package is marked with x64 but it has a schema less than 200. How do I do that using wix2? I'm already setting Platforms=x64 in my Package element, and all my Components now have Win64=yes on them. I think you want to set the InstallerVersion attribute of the Package element to be at least 200. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Unexpected German message box in msi file
Some messages come from the culture of the operating system no matter what the culture of the msi is. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Debbie Highgate Sent: Saturday, September 15, 2007 5:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Unexpected German message box in msi file When attempting to install my app, when another version has been installed, I initially get a message box with Installation wird vorbereitet. I set -culture:en-us during the linking phase, so how do I stop a German message appearing? Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now http://us.rd.yahoo.com/evt=48223/*http:/get.games.yahoo.com/proddesc?ga mekey=monopolyherenow (it's updated for today's economy) at Yahoo! Games. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IIS, Vista and WiX
The legacy administration objects are part of IIS. You have to make sure that they are installed before you start your installation. How do you check to make sure that IIS is installed? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lalande Sent: Friday, September 14, 2007 1:39 PM To: Rob Mensching Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] IIS, Vista and WiX So does this mean that these custom actions don't work on Vista? Is there anything I can do to get them to work as a temporary measure? What are legacy administration objects? John On 9/14/07, Rob Mensching [EMAIL PROTECTED] wrote: The custom actions require the legacy administration objects today. Maybe one day we'll update the IIS custom actions to not require that on Vista. It's a pretty large work item though. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lalande Sent: Friday, September 14, 2007 09:43 To: wix-users@lists.sourceforge.net Subject: [WiX-users] IIS, Vista and WiX I have completed the an installer that installs a ASP.Net 2.0 web application. It works fine in Windows 2003 Server but fails on Vista with the error message: Cannot connect to the Internet Information Server. (-2147221164 ) In the log file, the detail for the failure is: ConfigureIIs: failed to get IID_IMSAdminBase Object Error 26001. Cannot connect to Internet Information Server. (-2147221164 ) Is there anything special needed for Vista installs of a web site in IIS using WiX? John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IIS, Vista and WiX
I don't know how to tell if the legacy administration is installed. To install it via the GUI, start Programs and Features, click Turn Windows features on or off then drill down through IIS and Web Management tools and make sure that IIS 6 Management Compatibility is checked. To install it via the command line, use OCSetup.exe with the right command line arguments. To figure out what those arguments should be, download the WAIK (Windows Automated Installation Kit) which should document the arguments for each of the Windows features. Searching for WAIK may also do the trick. Good luck! From: John Lalande [mailto:[EMAIL PROTECTED] Sent: Friday, September 14, 2007 2:08 PM To: John Vottero Cc: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] IIS, Vista and WiX I check the value of the MajorVersion entry in the HKLM\SOFTWARE\Microsoft\InetStp registry key. Is there a way to check for the legacy administration objects? Also, how do you install them? John On 9/14/07, John Vottero [EMAIL PROTECTED] wrote: The legacy administration objects are part of IIS. You have to make sure that they are installed before you start your installation. How do you check to make sure that IIS is installed? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lalande Sent: Friday, September 14, 2007 1:39 PM To: Rob Mensching Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] IIS, Vista and WiX So does this mean that these custom actions don't work on Vista? Is there anything I can do to get them to work as a temporary measure? What are legacy administration objects? John On 9/14/07, Rob Mensching [EMAIL PROTECTED] wrote: The custom actions require the legacy administration objects today. Maybe one day we'll update the IIS custom actions to not require that on Vista. It's a pretty large work item though. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lalande Sent: Friday, September 14, 2007 09:43 To: wix-users@lists.sourceforge.net Subject: [WiX-users] IIS, Vista and WiX I have completed the an installer that installs a ASP.Net 2.0 web application. It works fine in Windows 2003 Server but fails on Vista with the error message: Cannot connect to the Internet Information Server. (-2147221164 ) In the log file, the detail for the failure is: ConfigureIIs: failed to get IID_IMSAdminBase Object Error 26001. Cannot connect to Internet Information Server. (-2147221164 ) Is there anything special needed for Vista installs of a web site in IIS using WiX? John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ZIP archive inside MSI, UNZIP after installation...
I need to include ZIP archive (documentation in any directory structure...) into MSI and after installation I need to unzip it. Does anybody any idea how to do it? Encapsulation of documentation's directory structure is not so useful for me... Why do you want to do this? The files will be compressed in the MSI by Windows Installer. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects
First a disclaimer, I haven't actually done this! VS Solutions are nothing but groups of projects, you can have one solution which has the projects you want to build and another solution that includes the Votive projects that you use with Visual Studio. It's not that hard to create an MSBuild file which describes how to build your WiX V2 or V3 code. Once you have your WiX MSBuild file, create a Team Foundation build type which builds the solution that doesn't reference WiX then edit the TFSBuild.proj file and add another SolutionToBuild... element that points to the WiX MSBuild file. Despite its name, the SolutionToBuild element can point at a solution or a project file and the project file just has to be valid MSBuild, it doesn't have to be something that Visual Studio can understand. Had a look at the files and I've finally got my head round this. As i understand it WiX v2 .wixproj files, which are used for VS integration, aren't MSBuild files. You have to create your own .wproj files for that. Which means that WiX v2 isn't compatible withTeam Build (as it tries to build the .wixproj file). It'd be really cool if v2 did support Team Build and it's solution centric build process. Without it we can't really consider using WiX v2 or v3 (as it's not stable yet). Which leads me to my next question, is there a rough time line for the switch to v3? Oh and in case it makes you feel better Justin I've been messing around with IS for two days and 2 hotfixes later i still can't get it to build with MS or Team! :-) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] GDI+ MergeModule
I don't think you need the CDATA for your condition. Conditions are
usually wrapped in CDATA because they often contain and characters.
That being said, are you sure that the problem is actually in the
fragment that you posted? Your CDATA looks fine to me, I'm thinking
that maybe something else is messing up the parsing and makes candle
think that you have a ]] in your CDATA. Do you have any other CDATAs
in this WiX file? If you remove that condition line, does it compile?
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of stian
Sent: Wednesday, August 29, 2007 2:34 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GDI+ MergeModule
Thanks for the suggestion, but it still gives the same error... Do I
have to
use CDATA to achieve what I want?
The component is now:
Component Guid={..} Id=C_GDI
Condition![CDATA[VersionNT=500 Or NOT Version9X=]]/Condition
File DiskId=1 Id=id1893 KeyPath=yes Name=gdiplus.dll
Vital=yes
src=gdiplus.dll /
/Component
And the error still:
candle.exe : error CNDL0001 : Cannot have ']]' inside an XML CDATA
block.
More suggestions are very welcome!
Brian Simoneau wrote:
Try this in your condition
![CDATA[VersionNT=500 Or NOT Version9X=]]
-Brian Simoneau
--
View this message in context:
http://www.nabble.com/GDI%2B-MergeModule-
tf4316091.html#a12392946
Sent from the wix-users mailing list archive at Nabble.com.
---
--
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a
browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] GDI+ MergeModule
Hi and thanks, I was thinking the same; that it was something outside this block that caused the problems. However, I don't have any more CDATAs or ]] in this WiX file. This file only contains a fragment, and I have another xml containing the product block. This file does not contain any CDATA either. The program is compiled and msi created using SCons, so there is a SConstruct file starting this. Unless this adds any extra outer xml behind the scenes there is no CDATA to be seen. Everything works fine when removing the condition line. You say that I probably don't need the CDATA. Do I get access to the parameters VersionNT and Version9X outside this? I'm sorry if I ask any stupid questions, but I'm new to WiX and haven't used CDATA before neither.. Yes, you still have access to VersionNT and Version9X. Try making your condition: ConditionVersionNT=500 Or NOT Version9x=/Condition John Vottero wrote: I don't think you need the CDATA for your condition. Conditions are usually wrapped in CDATA because they often contain and characters. That being said, are you sure that the problem is actually in the fragment that you posted? Your CDATA looks fine to me, I'm thinking that maybe something else is messing up the parsing and makes candle think that you have a ]] in your CDATA. Do you have any other CDATAs in this WiX file? If you remove that condition line, does it compile? -- View this message in context: http://www.nabble.com/GDI%2B-MergeModule- tf4316091.html#a12393572 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] x64 Compatibility
That’s correct but, if you want the app to run as a 64 bit app on a 64 bit O/S, you need two installers. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of barbq Sent: Monday, August 13, 2007 5:51 AM To: John Vottero; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] x64 Compatibility Thanks, This sounds like I can utilize the MSI, since my app single exe can run on both 64bit and 32bit. I understood everything you said and it makes sense - except for deploying a .NET app. As far as I know, a .NET app should be compiled only once for both 32bit and 64bit, no? On 8/13/07, John Vottero [EMAIL PROTECTED] wrote: You can create an installer that will install on both x64 and x86 in fact, most 32 bit MSIs will install and work just fine under x64 but, those applications run as 32 bit apps under the WOW64 emulator. What you can't do is create an MSI that installs a 32 bit app under x86 and a 64 bit app under x64 (even if the app is a .NET assembly that will run 32bit or 64bit). If you're OK with having your app run as a 32 bit app on a 64 bit O/S, then just create a 32 bit MSI and it will probably work just fine on a 64 bit O/S. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tal Shrestha Sent: Sunday, August 12, 2007 9:08 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] x64 Compatibility Could you elaborate on why this is true even though the x64 version utilizes the WOW64 emulator? (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/running_32_bit_applications.asp ) On 8/12/07, John Vottero [EMAIL PROTECTED] wrote: No, you cannot create one MSI for both x64 and x86. Windows Installer doesn't support that. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of barbq Sent: Sunday, August 12, 2007 7:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] x64 Compatibility Hello, I would like to compile an MSI using WIX that is targeted for both x86 and x64 machines. I've noticed features intended explicitly for x64 machines, however this does not suit my needs. Can one single MSI be compatible with both x64 and x86 machines? Thanks, Tal. -- Tal Shrestha | www.3dbe.com http://www.3dbe.com/ -- Tal Shrestha | www.3dbe.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] x64 Compatibility
No, you cannot create one MSI for both x64 and x86. Windows Installer doesn’t support that. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of barbq Sent: Sunday, August 12, 2007 7:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] x64 Compatibility Hello, I would like to compile an MSI using WIX that is targeted for both x86 and x64 machines. I've noticed features intended explicitly for x64 machines, however this does not suit my needs. Can one single MSI be compatible with both x64 and x86 machines? Thanks, Tal. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RefCounting
Windows installer does do reference counting but, it counts components not products. The problem with trying to reference count a whole product from the msi is that you don't know why the msi is being executed. Is your msi being executed because of a new install of product XYZ or a reinstall of product ABC? One would increment the reference count and the other wouldn't. You might take a look at creating a merge module which would get you reference counting at the component level. The problem with merge modules is that there isn't a good way to release an update of your product, you have to get the users of your product to release an update. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Diplomacy Player Sent: Monday, August 06, 2007 2:19 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] RefCounting I am writing a redist msi using wix and I need to ensure that my content only gets installed once and not uninstalled until all referencing installs have uninstalled. It would seem like Windows Installer would just handle this, but apparently it does not. Do I need to implement this myself? What's a good way to do it? Thanks, Paul - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapper?
You're confusing me. By tfs, do you mean Team Foundation Server? If so, how does it not support MSBuild? -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, July 30, 2007 12:39 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] bootstrapper? jcafaro10 wrote: Figured it out. This works provided there are product .xml files where I need them to be. Problem is I'll have to generate this manually b/c this is for msbuild not wix and tfs doesn't support msbuild apparently Edit: Actually I was thinking what if I just had an action in my wixfile that ran the command line argument necessary to create the bootstrapper? That should be ok right? I know I use the ExeCommand to do command line stuff but I need a command to change to the right directory and one to use the command...How do I use more than one execommand in an action? Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductNameMicrosoft .NET Framework/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.SQL.Server.Desktop.Engine ProductNameMicrosoft SQL Server/ProductName /BootstrapperFile BootstrapperFile Include=iTech.Logger ProductNameiTech/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=WixProject1.msi ApplicationName=Wix Sample BootstrapperItems=@(BootstrapperFile) OutputPath=.\bin\Debug ComponentsLocation=Absolute ComponentsUrl=put my file path here Culture=en / /Target /Project John Vottero wrote: I know that to install .NET I need to use a bootstrapper so I made a .proj file and put this in it, but I need to add other things to the bootstrapper that won't install from the msi like sql server desktop engine and itechlogger but I'm not sure how to do that. SQL Server Express can be installed by adding another BootstrapperFile to your ItemGroup. If you google BootstrapperFile, you will find information on creating your own bootstrapper files so, worst case, you would have to create a Bootstrapper file for itechlogger. Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductNameMicrosoft .NET Framework 2.0/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=WixProject1.msi ApplicationName=Wix Sample BootstrapperItems=@(BootstrapperFile) OutputPath=.\bin\Debug ComponentsLocation=HomeSite Culture=en / /Target /Project -- View this message in context: http://www.nabble.com/bootstrapper-- tf4171003.html#a11866122 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/bootstrapper-- tf4171003.html#a11866776 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX
Re: [WiX-users] bootstrapper?
You must be using Votive, the Visual Studio plugin for WiX. I don't use that so, I'm not sure I can help. But, the xml file that you have for creating the bootstrapper is essentially a Visual Studio project. You might try adding it to the solution that your WiX project is in, it might work. Make sure you have a backup because it might blow up in your face too! From: JP Cafaro [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 12:58 PM To: John Vottero Subject: Re: [WiX-users] bootstrapper? Not sure, he's not in today, but I've been doing pretty well with Wix and it seems very straight forward. Does Wix have prebuild commands? Or something like that so I can have the bootstrapper get made without having to manually go to the command line? On 7/30/07, John Vottero [EMAIL PROTECTED] wrote: Ok, TFS supports MSBuild. What isn't working? From: JP Cafaro [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 12:51 PM To: John Vottero Subject: Re: [WiX-users] bootstrapper? Team Foundation Server. I honestly don't know. My product manager just told me to look into Wix because TFS supports it On 7/30/07, John Vottero [EMAIL PROTECTED] wrote: You're confusing me. By tfs, do you mean Team Foundation Server? If so, how does it not support MSBuild? -Original Message- From: [EMAIL PROTECTED] [mailto: wix-users- mailto:wix-users- [EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, July 30, 2007 12:39 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] bootstrapper? jcafaro10 wrote: Figured it out. This works provided there are product .xml files where I need them to be. Problem is I'll have to generate this manually b/c this is for msbuild not wix and tfs doesn't support msbuild apparently Edit: Actually I was thinking what if I just had an action in my wixfile that ran the command line argument necessary to create the bootstrapper? That should be ok right? I know I use the ExeCommand to do command line stuff but I need a command to change to the right directory and one to use the command...How do I use more than one execommand in an action? Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003 ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductNameMicrosoft .NET Framework/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.SQL.Server.Desktop.Engine ProductNameMicrosoft SQL Server/ProductName /BootstrapperFile BootstrapperFile Include=iTech.Logger ProductNameiTech/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=WixProject1.msi ApplicationName=Wix Sample BootstrapperItems=@(BootstrapperFile) OutputPath=.\bin\Debug ComponentsLocation=Absolute ComponentsUrl=put my file path here Culture=en / /Target /Project John Vottero wrote: I know that to install .NET I need to use a bootstrapper so I made a .proj file and put this in it, but I need to add other things to the bootstrapper that won't install from the msi like sql server desktop engine and itechlogger but I'm not sure how to do that. SQL Server Express can be installed by adding another BootstrapperFile to your ItemGroup. If you google BootstrapperFile, you will find information on creating your own bootstrapper files so, worst case, you would have to create a Bootstrapper file for itechlogger. Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003 ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductNameMicrosoft .NET Framework 2.0/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=WixProject1.msi ApplicationName=Wix Sample BootstrapperItems=@(BootstrapperFile) OutputPath=.\bin\Debug ComponentsLocation=HomeSite Culture=en / /Target /Project -- View this message in context: http://www.nabble.com/bootstrapper-- tf4171003.html#a11866122 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find
Re: [WiX-users] how to change msi working for 32 bit os to work for 64 bit os
i m having msi of my product which is working on all 32 bit windows versions now iwant to create msi which will wirk for bith 32 and 64bit os or will work for 64 bit os. i have no idea what r the changes i m suppose to make in my msi. You need to make a copy of your 32bit WiX source (you can't have a single installer for both 32 bit and 64 bit). In the 64 bit copy, you need to change: Product/@Id=new guid Product/@UpgradeCode=new guid Package/@Id=new guid Package/@Platforms=x64 For each component: Component/@Guid=new guid Component/@Win64=yes You may need to add Win64=yes when referencing the registry too. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] DigitalCertificate is ignored
I don't think that DigitalCertificate is what you want. I think that is used when you want to verify the signature of an external resource (CAB file etc). Sign your msi's with SIGNTOOL.EXE, the MSBuild SignFile task or PowerShell's Set-AuthenticodeSignature cmdlet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, July 23, 2007 10:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] DigitalCertificate is ignored I'm relatively new to Widows Installer and WiX and am attempting to create a signed installer. I've added the following to my wxs file: Media Id=1 Cabinet=MyProduct1.cab EmbedCab=yes DiskPrompt=CD-ROM #1 DigitalCertificate Id=MyCertificate SourceFile=..\Dependencies\CodeSigning\Certificate\mycredentials.spc / /Media Candle and Light run successfully without errors or warnings but the resulting MSI file does not appear to be signed. Is this just signing the cab file and not having any effect on the MSI? I can't find much documentation on how to get a signed MSI from WiX. Thanks, Doug - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] AdminLetterCitrix virtualization, Windows Vista, and more
The makers of InstallShield are spamming the WiX users mailing list??? That's a good way to make friends. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Macrovision Sent: Wednesday, July 18, 2007 2:59 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] AdminLetterCitrix virtualization, Windows Vista, and more http://www.installshield.com/graphics/email/email_template/newsletter/m vsn_logo.gif July 2007, Volume 8, Issue 3 AdminLetter Topics in this Issue: * AdminStudio 8.5 prevents DLL conflicts with Citrix virtualization support * AdminStudio wins two 2007 Redmond Readers' Choice Awards * Tip: Setting isolation options for Citrix virtual profiles * Save time by indentifying which applications to repacakge for Windows Vista * AdminStudio training special: Sign up with co-workers and save! Resources Downloadable Resources http://mktg.macrovision.com/mk/get?_EC=sDP6ufdO6Qm9Rk7u7zetN2 Tip Archive http://mktg.macrovision.com/mk/get?_EC=gc6R8JBje3eR9pm1PWcWXY User Community http://mktg.macrovision.com/mk/get?_EC=8jXiniNmi1akMRniOZCn9M Read It Online http://mktg.macrovision.com/mk/get?_EC=C119zsnMlFeySE6mntQCaA Suggestions Feedback mailto:[EMAIL PROTECTED] http://www.macrovision.com/images/products/logos/adminstudio_tile.gif AdminStudio 8.5 prevents DLL conflicts with Citrix virtualization support The new AdminStudio(r) 8.5 is now available, and it helps you put an end to DLL conflicts with support for Citrix(r) application virtualization. AdminStudio 8.5 can quickly convert applications into Citrix virtual packages you can stream with Citrix Presentation Server(tm). Applications run in their own virtual containers - no more conflicts. And no conflict testing! Plus, AdminStudio 8.5 also includes the new InstallShield(r) 2008, with robust MSI editing tools for ensuring applications are compatible with Windows Vista(tm). * Try it for yourself! Begin a no-cost evaluation of AdminStudio 8.5 http://mktg.macrovision.com/mk/get?_EC=30z9XXEIixMitNx4unr-iY * Register for the AdminStudio 8.5 QuickStart webinar http://mktg.macrovision.com/mk/get?_EC=XjdX8a2WngyvPuiwlcrFhY * Visit the AdminStudio 8.5 Web page http://mktg.macrovision.com/mk/get?_EC=EQALKrStK8Qb8dA860rV-E top AdminStudio wins two 2007 Redmond Readers' Choice Awards For the second year in a row, Macrovision's AdminStudio has won the 2007 Redmond Readers' Choice Awards for Best Software Packaging Product and Best Application Conflict Testing Tool. AdminStudio also took home both honors in 2006. Thanks to everyone who voted for AdminStudio once again! See the complete list of winners http://mktg.macrovision.com/mk/get?_EC=YLjz3H6ZHxeEaigyQOj9lI top Tip: Setting isolation options for Citrix virtual profiles Macrovision's AdminStudio makes it easy to edit any aspect of Citrix virtual profiles, from modifying registry settings to controlling isolation options at a granular level. This tip explains the different isolation options for Citrix virtual profiles and how you can use AdminStudio to set them. Read the tip (pdf) http://mktg.macrovision.com/mk/get?_EC=_KfkoCfzeGQ-ohSxhp8EC2 top Save time by identifying which applications to repackage for Windows Vista AdminStudio automatically pinpoints which of your legacy applications need to be repackaged for Windows Vista and which do not, so you don't waste time with unnecessary work. AdminStudio will correct any issues to ensure your mission-critical applications are compatible with Windows Vista. Learn more about how Macrovision simplifies Vista migrations http://mktg.macrovision.com/mk/get?_EC=PbixbsYUUsUDGp8DhoM7PY top AdminStudio training special: Sign up with co-workers and save! Becoming an AdminStudio expert helps IT professionals excel, and now's the perfect time to do it. Take an AdminStudio class in July, August, or September of 2007 and save! You'll get the AdminStudio skills you need to make your job easier, and you can save 10% when you register 2-4 people or save 15% when you sign up 5 or more! Sign up today http://mktg.macrovision.com/mk/get?_EC=rlVkhIgv-tICvEoEfHDVuU top Boost your productivity with training from the experts Accelerate your software packaging and deployment process with expert training http://www.macrovision.com/services/education/1988.htm . Our certified instructors will teach you more about AdminStudio than anyone else. New Public Training Schedule AdminStudio, Repackaging and Migration Workshop http://www.installshield.com/graphics/common/triangle_rt.gif July 23-27, Santa Clara, CA http://mktg.macrovision.com/mk/get?_EC=IH9Wk47E5jAt0n4KLPembM http://www.installshield.com/graphics/common/triangle_rt.gif July 30-Aug 3, Maidenhead, UK http://mktg.macrovision.com/mk/get?_EC=OG764esH_pmPu9ZChEO7FE http://www.installshield.com/graphics/common/triangle_rt.gif Aug 13-17 , Schaumburg, IL
Re: [WiX-users] Creating a service using WIX
I get the following error while running the .msi created by using the following code to create a service using WIX.GService.exe is the service exe file.I've copied installutillib.dll,GService.exe to the wix-binary folder(folder where candle.exe and light.exe exists)and created a service.xml file with the line given at the end You should dump all the InstallUtilLib stuff and replace it with ServiceInstall and ServiceControl elements. InstallUtilLib is undocumented, unsupported and, in your case, there are better alternatives. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] one installer launches another
You have to use a bootstrapper, you don't have to write one. Take a look at the GenerateBootstrapper task or dotNetInstaller or NSIS. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 11:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] one installer launches another I know this has been asked before, but is there still no way to launch another installer from another. Apparently, for msxml60, Microsoft has abandoned the merge module approach and is only distributing an msi which they recommend you launch silently from you current installer. I would like to do that if possible. Or do I have to write a bootstrapper exe? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Converting Setup project to WiX 3.0 project (Custom Actions)
-Original Message- From: W. Craig Trader [mailto:[EMAIL PROTECTED] Sent: Thursday, July 12, 2007 12:36 PM To: John Vottero Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Converting Setup project to WiX 3.0 project (Custom Actions) John Vottero wrote: It would be very easy to write a console app that calls the C# Installer based code. Once you have that, use the WiX CAQuietExec custom action to run the console app. [snip] I'm thinking that I need to use the InstallUtil.exe console-app to run my code (since the code expects to be run that way for the old VS Setup project). Do you have any explicit examples (or pointers to examples) of how to use the QAQuietExec custom action? I'm still pretty new to WiX... It's basically a two step process, set a property with the value of the command line like this: CustomAction Id=SetCreateDB Property=CreateDB Value=quot;[#JAMSDBAEXE]quot; INSTALL/UI=[UILevel]/ And then execute that command line with CAQuietExec like this: CustomAction Id=CreateDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ You'll also have to schedule those two custom actions in the InstallExecuteSequence The hard part is getting the Value right in the first step. [#JAMSDBAEXE] resolves to the full path of an executable that we just installed. I'm not sure how you get the full path to InstallUtil, I think with FileSearch. Also, you've mentioned rolling back if the DB update fails, I'm not sure if that's going to work or not. We treat DB updates as something that happens *after* the installation. If our DB update fails, the DB updates rollback but, the product install doesn't. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Starting two services in one installation?
Try: SC DELETE ServiceName from a command window. Also, you really want to use Virtual Machines with undo disks enabled for testing installers. I don't know how I ever lived without them. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton Sent: Saturday, July 07, 2007 7:56 PM To: 'Bob Arnson' Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Starting two services in one installation? So I setup Wix wrong in trying to get the service to install. Now it is installed with no service control. Do you know how to remove it? It seems that now when I try to install I get an error with ServiceInstall. I think this is because the service has not been removed. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, July 07, 2007 2:31 PM To: Kevin Burton Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Starting two services in one installation? Kevin Burton wrote: By the way if I don't start the service and just install it, it is not removed on uninstall. You still need ServiceControl to delete services during uninstall. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] version numbering
We use environment variables, like this: ...Name=JAMS Version $(env.Version) Version=$(env.Version) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Steele Sent: Monday, July 02, 2007 10:59 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] version numbering Hi, I have my version number hardcoded in multiple locations throughout my wxs file eg Product Name='Matador 2.1.1' Version='2.1.1.0' Manufacturer='FBBT Limited' Id='F5E0DFC0-7086-49a7-B068-DAB66E84A0BC' Language='1033' UpgradeCode='080075AA-7BEA-46f6-A4A9-96C7279C4F92' Codepage='1252' Package Comments='Matador is a registered trademark of FBBT Ltd.' Compressed='yes' Description='Matador 2.1.1 installer' InstallerVersion='211' Keywords='Matador 2.1.1 installer' Languages='1033' Manufacturer='FBBT Limited' SummaryCodepage='1252' / Is it possible for me to parameterise this, something along the lines of eg Property Id='MatadorVersionNumber' Value='2.3'/ Feature Id='CompleteFeature' Title='Matador [MatadorVersionNumber]' Description='Matador [MatadorVersionNumber]' Display='expand' Level='1' ConfigurableDirectory='INSTALLDIR' AllowAdvertise='no' InstallDefault='local' Absent='disallow' Feature Id='MainProgram' Title='Matador [MatadorVersionNumber] Runtime' Description='Setup files necessary for Matador [MatadorVersionNumber]' Level='1' AllowAdvertise='no' InstallDefault='local' Absent='disallow' By the way, the code above works for the Description fields but NOT for the Title fields :( Or is there a better way that people do this? Thanks for any help, Patrick - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing dotnet framework along with your MSI package
Google GenerateBootstrapper task. That's what a Visual Studio 2005 project uses and it will work with a WiX generated MSI too. The example in MSDN for the GenerateBootstrapper task shows the .NET Framework as a prerequisite. Forget about trying to install the .NET Framework from a CA, you're asking for trouble doing that. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierson Lee (Volt) Sent: Monday, July 02, 2007 8:20 PM To: sanjay bhaskar; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing dotnet framework along with your MSI package That's the same thing I'm doing. You have to use a bootstrapper. If you're using VS 2005, you can use the setup project and it will allow you to check for .net framework . The other way you can do it (which I did, but am having a heck of a time) is to call the .net Framework redistributable at the end using a custom action , but it has to be set after InstallFinalize so that your wix windows installer instance ends when your dotnetfx.exe is called. I did it this way and it works, although I don't know the consequences of this beyond installing the framework AFTER your application. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sanjay bhaskar Sent: Monday, July 02, 2007 4:52 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing dotnet framework along with your MSI package How to include dotnet framework redistributable package (dotnetfx.exe) as a part of your own installation package (MSI) such that the dotnet framework gets installed during your installation process(Like through customActions). the error i get is that another installation is already in progress. How to get out of this problem and install the dotnetfx. Thanks Make every IM count. Download Windows Live Messenger and join the i'm Initiative now. It's free. Make it count! http://im.live.com/messenger/im/home/?source=TAGWL_June07 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Replacing the stock bitmaps
The cannot display webpage problem with the chm is caused by the file being marked as downloaded from another computer. Right click on the chm and pick Properties, there should be an Unblock button near the bottom on the first tab. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, June 28, 2007 11:13 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Replacing the stock bitmaps In earlier wix v3 builds you could add a Bitmaps dir and replace bannrbmp.bmp and dlgbmp.bmp with your own images. But in 3.0.2925.0, that doesn't seem to work. How am I supposed to override the stock bitmaps in this version? I have listed a blurb from the article below. Also, can anyone view the chm file that comes in the zip download for this version? Every page returns cannot display webpage like all the links are bad. Is it just me? From the v2 manual online: http://wix.sourceforge.net/manual-wix2/WixUI_dialog_library.htm Replacing the stock bitmaps The WixUI dialog library includes stock bitmaps for the background of the welcome and installation-complete dialogs and the top banner of the other dialogs. You can override those graphics with your own for product-branding purposes. To replace stock bitmaps, add the files from the table below to a subdirectory named Bitmaps under your WiX source file. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Calling a .bat file from WIX
No, WiX does NOT use gacutil.exe From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alperstein, Kenny Sent: Tuesday, June 26, 2007 9:54 AM To: Mike Dimmick; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Calling a .bat file from WIX Mike, One last question. Does the WIX GACing functionality require that gacutil.exe be installed on the target machine? And does WIX assume it is installed in any particular place? Kenny Alperstein Framework Architect Protection Architecture - Frameworks Allstate Insurance Company ( Office: (847) 667-5552 + [EMAIL PROTECTED] From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 3:40 PM To: Alperstein, Kenny; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Calling a .bat file from WIX You should be adding files to the GAC using the Assembly=.net attribute on File, and consider using the WebVirtualDir element to add a virtual directory. Note that if you specify Assembly=.net, the file will only be installed to the GAC. If you also need a copy installed elsewhere, you will have to list the file again in a different Component and using a different Id. Recent versions of WiX will ensure that the file is only listed in the CAB once (according to Rob). The more declarative you can go, the better. Using the built-in features of Windows Installer and WiX means that someone else has tested install, uninstall, rollback, repair scenarios. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alperstein, Kenny Sent: 21 June 2007 17:58 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Calling a .bat file from WIX I am new to WIX and converting an existing process to WIX. I have a .bat file which call .cmd files to gac dlls and create a virtual directory? Is there a way to execute a .bat file in WIX or should I be using custom actions to create the virtual directory and call gacutil.exe to gac the dlls? Kenny Alperstein Framework Architect Protection Architecture - Frameworks Allstate Insurance Company ( Office: (847) 667-5552 + [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64 bit newbie question
I have a RegistrySearch tag that attempts to look up values in Root='HKLM' Key='Software\Microsoft\Shared Tools\Web Server Extensions\12.0' but on 64 bit machines, it ends up searching for HKLM\Software\Wow6432Node\Microsoft\Shared Tools\Web Server Extensions\12.0 (according to Process Monitor), which yields thw wrong result. Where does the Wow6432Node part come from? I am guessing that it means my MSI is running in 64 bit mode, but I am not sure what the proper solution is. (Using WIX 2.x) Thanks! Windows Installer thinks that it's a 32bit installer being installed on a 64 bit system so, it looks in the 32bit compatibility area of the registry (Wow6432Node). You need to set Win64=yes on the RegistrySearch element. I'm not sure if that's all you need to do or not, I've never tried to access the 64 bit registry from a 32 bit MSI. Do you want a 32bit or 64bit installer? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] msi to exe
We use iexpress to bundle everything into a self extracting executable. We then add a manifest to that executable and sign it. When the self extracting executable unpacks, it runs our bootstrapper which does all the detecting etc. and then invokes msiexec with the correct parameters. From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 10:09 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe It was clearly purposed for packaging IE, it always was. Now it also seems to have become repurposed as a generic basic solution. Now that it leaked into the OS it probably is fair game. Heck, I just read a TechNet article suggesting it's use for slipping things into a Sysprep postinstall via cmdlines.txt. Go figure... So I guess if it meets your needs, rock on. Personally I need a lot more power and flexibility in my bootstrappers. I can't see how IExpress could even begin to provide proper servicing in terms of UAC manifests, caching of packages, detecting installed products and performing upgrades, installing prereqs ectera so it's of no use to me. John Vottero [EMAIL PROTECTED] wrote: What says it's for packaging IE not other apps? From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 8:24 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Yes but it still says it's for packaging IE not other apps. I don't know how to touch this one to tell you the truth. John Vottero [EMAIL PROTECTED] wrote: wrote: I have never installed the Internet Explorer 7 Administration Kit and yet, I have IExpress.exe. Why do you think that license covers IExpress? From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:31 PM To: Christopher Painter; John Vottero; Afshin Sepehri; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] msi to exe I'm reading this page: http://www.microsoft.com/technet/prodtechnol/ie/ieak7/eula.mspx And I don't see any rights to use iexpress in the way that I read it being described here. Christopher Painter [EMAIL PROTECTED] wrote: Is this legal? Does Micrososft convey redist rights to reuse this as a generic bootstrapper? John Vottero [EMAIL PROTECTED] wrote: We use IExpress as part of an automated daily build. Do iexpress.exe /? to see the command line switches. From: Afshin Sepehri [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:06 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe I need this to be done as part of an automatic daily build process which also creates the .msi file. I am not sure if IExpress can be used for this purpose. Any alternative? Afshin From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 PM To: Afshin Sepehri; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Use IExpress.exe. You probably already have it (it's part of IE). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 4:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email
Re: [WiX-users] msi to exe
We use IExpress as part of an automated daily build. Do iexpress.exe /? to see the command line switches. From: Afshin Sepehri [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:06 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe I need this to be done as part of an automatic daily build process which also creates the .msi file. I am not sure if IExpress can be used for this purpose. Any alternative? Afshin From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 PM To: Afshin Sepehri; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Use IExpress.exe. You probably already have it (it's part of IE). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 4:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] msi to exe
You don't redistribute iexpress.exe, you redistribute the output of iexpress.exe. I still don't know if that's legal. From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:28 PM To: John Vottero; Afshin Sepehri; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] msi to exe Is this legal? Does Micrososft convey redist rights to reuse this as a generic bootstrapper? John Vottero [EMAIL PROTECTED] wrote: We use IExpress as part of an automated daily build. Do iexpress.exe /? to see the command line switches. From: Afshin Sepehri [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:06 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe I need this to be done as part of an automatic daily build process which also creates the .msi file. I am not sure if IExpress can be used for this purpose. Any alternative? Afshin From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 PM To: Afshin Sepehri; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Use IExpress.exe. You probably already have it (it's part of IE). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 4:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email http://us.rd.yahoo.com/evt=48225/*http:/new.toolbar.yahoo.com/toolbar/f eatures/mail/index.php wherever you're surfing. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] msi to exe
I have never installed the Internet Explorer 7 Administration Kit and yet, I have IExpress.exe. Why do you think that license covers IExpress? From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:31 PM To: Christopher Painter; John Vottero; Afshin Sepehri; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] msi to exe I'm reading this page: http://www.microsoft.com/technet/prodtechnol/ie/ieak7/eula.mspx And I don't see any rights to use iexpress in the way that I read it being described here. Christopher Painter [EMAIL PROTECTED] wrote: Is this legal? Does Micrososft convey redist rights to reuse this as a generic bootstrapper? John Vottero [EMAIL PROTECTED] wrote: We use IExpress as part of an automated daily build. Do iexpress.exe /? to see the command line switches. From: Afshin Sepehri [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:06 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe I need this to be done as part of an automatic daily build process which also creates the .msi file. I am not sure if IExpress can be used for this purpose. Any alternative? Afshin From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 PM To: Afshin Sepehri; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Use IExpress.exe. You probably already have it (it's part of IE). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 4:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email http://us.rd.yahoo.com/evt=48225/*http:/new.toolbar.yahoo.com/toolbar/f eatures/mail/index.php wherever you're surfing. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Don't be flakey. Get Yahoo! Mail for Mobile http://us.rd.yahoo.com/evt=43909/*http:/mobile.yahoo.com/mail and always stay connected http://us.rd.yahoo.com/evt=43909/*http:/mobile.yahoo.com/mail to friends. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] msi to exe
What says it's for packaging IE not other apps? From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 8:24 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Yes but it still says it's for packaging IE not other apps. I don't know how to touch this one to tell you the truth. John Vottero [EMAIL PROTECTED] wrote: wrote: I have never installed the Internet Explorer 7 Administration Kit and yet, I have IExpress.exe. Why do you think that license covers IExpress? From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:31 PM To: Christopher Painter; John Vottero; Afshin Sepehri; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] msi to exe I'm reading this page: http://www.microsoft.com/technet/prodtechnol/ie/ieak7/eula.mspx And I don't see any rights to use iexpress in the way that I read it being described here. Christopher Painter [EMAIL PROTECTED] wrote: Is this legal? Does Micrososft convey redist rights to reuse this as a generic bootstrapper? John Vottero [EMAIL PROTECTED] wrote: We use IExpress as part of an automated daily build. Do iexpress.exe /? to see the command line switches. From: Afshin Sepehri [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 5:06 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe I need this to be done as part of an automatic daily build process which also creates the .msi file. I am not sure if IExpress can be used for this purpose. Any alternative? Afshin From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 PM To: Afshin Sepehri; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] msi to exe Use IExpress.exe. You probably already have it (it's part of IE). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 4:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email http://us.rd.yahoo.com/evt=48225/*http:/new.toolbar.yahoo.com/toolbar/f eatures/mail/index.php wherever you're surfing. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Don't be flakey. Get Yahoo! Mail for Mobile http://us.rd.yahoo.com/evt=43909/*http:/mobile.yahoo.com/mail and always stay connected http://us.rd.yahoo.com/evt=43909/*http:/mobile.yahoo.com/mail to friends. Luggage? GPS? Comic books? Check out fitting gifts for grads http://us.rd.yahoo.com/evt=48249/*http:/search.yahoo.com/search?fr=oni_ on_mailp=graduation+giftscs=bz at Yahoo! Search. The fish are biting. Get more visitors http://us.rd.yahoo.com/evt=49679/*http:/searchmarketing.yahoo.com/arp/s ponsoredsearch_v2.php?o=US2140cmp=Yahooctv=Q107Taglines=Ys2=EMb=50 on your site using Yahoo! Search Marketing. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2
Re: [WiX-users] Fwd: Changing PowerShell ExecutionPolicy via Registry or Powershell Cmdlet
I'm trying to decide whether to change the PowerShell ExecutionPolicy setting either by modifying the registry entry or by running the Set-ExecutionPolicy cmdlet in PowerShell. Has anyone any opinions on which way is better/more proper? Thank you in advance. Neither would be proper, you should not change that policy with an installer. If the site has set the policy via Group Policies, you won't be able to change it. Why do you want to change it? Why don't you simply sign your scripts? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] preventing the overwrite of Shortcut
I believe that a major upgrade is essentially an uninstall of the old
version followed by an install of the new version.
I *think* you can get the effect you want by sequencing RemoveShortcuts
after CreateShortcuts but, I don't know what side effects you have to
watch out for.
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Jeff Paulsen
Sent: Tuesday, June 19, 2007 1:58 PM
To: 'Rob Mensching'; [EMAIL PROTECTED]; wix-
[EMAIL PROTECTED]
Subject: Re: [WiX-users] preventing the overwrite of Shortcut
Certainly there are better places for configuration data. The
advantage
to
command-line options is that you can edit them without starting the
application, so to keep that benefit, I'd have to provide a separate
configuration tool. I'm not opposed to doing that later this week, but
having shortcuts that live through an upgrade will make my customer
happy
tonight.
It seemed that setting NeverOverwrite on the Component element was
simpler.
I just can't figure out why my shortcut would be overwritten during an
upgrade anyway. The guid hasn't changed. The keypath hasn't changed.
Does
anybody know why this doesn't do what I expected?
Jeff Paulsen
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Tuesday, June 19, 2007 10:11 AM
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] preventing the overwrite of Shortcut
Beyond what Richard suggests below, you'll have to write a block of
custom code to do the migration of user data. Possible but mostly
annoying. smile/
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, June 19, 2007 10:02 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] preventing the overwrite of Shortcut
I think my question would be why the user is forced into a (somewhat
unfriendly) specification of command line parameters as opposed to a
friendlier scenario using (for example) a configuration file, or a
configuration interface that stores things somewhere appropriate.
You may want to take a closer look at the design here. What is the
user
specifying via the shortcut which can apparently not be handled
through
a better mechanism?
Just my $.02.
Regards,
Richard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Paulsen
Sent: Tuesday, June 19, 2007 12:39 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] preventing the overwrite of Shortcut
I have a Wix installer that includes something like this:
Component Id=MyShortcuts NeverOverwrite=yes
Guid={someguid}
RegistryKey Action=create Id=MyShortCutsRegKey
Key=Software\TheCompany\TheProduct 1.0\My Root=HKCU
RegistryValue Id=MyShortcutsKeyVal KeyPath=yes
Name=MyShortcuts Type=string Value=present /
/RegistryKey
Shortcut Id=MyStartMenu Directory= TheProduct
MenuDirectory
Name=TheProduct 1.0 Icon=TheProduct.exe IconIndex=0
WorkingDirectory=INSTALLLOCATION Advertise=no
Target=[#TheProduct.exe]
/
Shortcut Id=MyDesktop Directory=DesktopFolder
Name=TheProduct
1.0 Icon=TheProduct.exe IconIndex=0
WorkingDirectory=INSTALLLOCATION
Advertise=no Target=[#TheProduct.exe] /
/Component
After installation, my users frequently add command-line flags to
the
shortcut. When they upgrade to a new version, their shortcuts are
overwritten, losing the command-line flags. I added the
NeverOverwrite
attribute to the Component, but it didn't have any effect.
All my upgrades are done with Product Id=*, so they're all major
upgrades.
Am I doing something wrong with my Wix? Failing that, is there any
reasonable way to preserve the command-line parameters my users have
added
to the shortcut?
Thanks,
Jeff Paulsen
-
---
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the
individual or entity to whom it is addressed. If you have received
this communication in error, be aware that forwarding it, copying
it,
or in any way disclosing its content to any other person, is
strictly
prohibited. Quixote Traffic Corporation is neither liable for the
contents, nor
Re: [WiX-users] How to install files, run an action, then delete the files??
If the CA fails, you expect the entire installation to rollback, right? If so, then the CA has to scheduled before InstallFinalize because InstallFinalize is the “commit” so a failure after that won’t rollback what happened before InstallFinalize. I think your next problem is going to be that you can’t schedule your CA before InstallFinalize because the NAnt files aren’t available for use until after InstallFinalize. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, June 06, 2007 5:20 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to install files, run an action, then delete the files?? The custom action isn't the problem it is all the regular files put down by the installer that don't roll-back -Original Message- From: Bob Arnson To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Sent: Wed, 6 Jun 2007 6.01am Subject: Re: [WiX-users] How to install files, run an action, then delete the files?? [EMAIL PROTECTED] wrote: I have an MSI which installs files by dropping them in specific directories. It then runs a custom action which may mail. If it fails, the MSI reports there has been a problems and the progress bar goes backwards. Normally this is the point where it will remove all the files it dropped onto the target system, but in this case it doesn't remove them. When is the CA scheduled? MSI rolls back only during the installation transaction, so anything after InstallFinalize won't roll back, for example. -- sig://boB http://joyofsetup.com/ Get a FREE AOL Email account with 2GB of storage. Plus, share and store photos and experience exclusively recorded live music Sessions from your favourite artists. Click Here http://info.aol.co.uk/joinnow/?ncid=548 for more information. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] x64 and x86 both use same data files
It sounds like you're trying to create a single MSI that installs either 32 bit or 64 bit executables, is that correct? If so, you shouldn't, you need one MSI for 32 bit and one for 64 bit. I don't think you want to reference ProgramFiles64Folder either. Use ProgramFilesFolder and Windows Installer will put things in the correct directory based upon the Component's Win64 setting. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Magus Sent: Wednesday, June 06, 2007 4:51 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] x64 and x86 both use same data files The problem: Currently I have a data component that installes to ProgramFilesFolder, but on a x64 machine it will install my executable to ProgramFiles64Folder and the data needs to be in relation to it. On X64 the x86 program files will not install. Is there a way to accomplish this task. Directory Id =ProgramFiles64Folder ... Component = Main64Component GUID = PUT-GUID- HERE.../Component /Directory Directory Id = ProgramFilesFolder ... Component =MainComponent GUID = PUT-GUID-HERE .../Component Directory Id = DataFolder ... Component = DataComponent GUID = PUT-GUID-HERE ... /Component /Directory /Directory What I want is on X64 the DataFolder points to \\Program Files\\DataFolder\\ instead of \\Program Files (x86)\\DataFolder\\ Is there a conditional way to do this or do I need a custom action that sets the Data Folder Directory according if the system is x64 -- View this message in context: http://www.nabble.com/x64-and-x86-both- use-same-data-files-tf3880360.html#a10997038 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Looking for advanced UI examples
I don't think it makes much difference if you use WiX V2 or V3 because they both wind up producing an MSI. However, V3 includes a bootstrapper so that might be a good example. I haven't looked at it so I don't know if it does what you need. When we were doing this, I found lots of bootstrappers many even had source code but, none of them did everything we needed them to do and, all the ones with source were written in unmanaged C++. So, we wound up writing our own in C#. There really was nothing hard, it was just a bunch of UI to figure out which commands to send to Process.Start and, it was a lot easier doing that UI in C# than in Windows Installer with C++ custom actions. That sounds reasonable. How do I get started? Are you aware of samples of doing something like this in a bootstrapper? (preferrably with WIX 2.x, but we would consider switching to 3.x if there was a good reason to) Thanks! John Vottero wrote: It's much easier to do 1, 2 and 3 in a bootstrapper which then executes your WiX created MSI. The following sequence of tasks seem like they would be common and I am hoping that someone has a working example of doing this in WIX: 1. Prompt the user for information about which (new or existing) service account should be used. 2. Prompt the user for information about the SQL database that needs to be created (select from a list of SQL Instances, verify connection and creation rights, etc.) 3. Prompt the user for information about the web app that needs to be set up (select from existing sites or prompt for host/port/name to create a new site) 4. Create the necessary accounts, SQL database, web site, web app as specified above. I have found a number of examples of doing #4, all of which use hard- coded values for the information I want to prompt for in #1 - 3. Building a nice interactive UI like I see in various Microsoft installers seems like a lot of tedious work, especially if we have to start from scratch writing lots of custom actions. Does WIX have more support for this than I realize, or are there less-trivial examples out there? -- View this message in context: http://www.nabble.com/Looking-for- advanced-UI-examples-tf3865328.html#a10950077 Sent from the wix-users mailing list archive at Nabble.com. - -- -- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Looking-for- advanced-UI-examples-tf3865328.html#a10951258 Sent from the wix-users mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional default Folder?
People I work for now want our installer only to install the best version instead of x64 and x86 on the end user machine. I have my ProgramFilesFolder as the main directory, however I would like it to be ProgramFiles64Folder if it is a x64 machine. Is there a conditional way to do this, or do I want to make a custom action set this property before I install. You have to have two MSIs, one for x64 and one for x86. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista unknown publisher
I've just been looking at buying a cert and I'm wondering why Verisign is so expensive. Why would someone pay 2 or 3 times more? Is there any difference between what you get from Verisign, Thawte or GlobalSign? -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Rennie Petersen Sent: Wednesday, May 30, 2007 7:43 AM To: Pseudonymic Wannabe; [EMAIL PROTECTED]; wix- [EMAIL PROTECTED] Subject: Re: [WiX-users] Vista unknown publisher I bought a digital certificate from GlobalSign a couple of months ago. It cost approx. 1/3 what Verisign wanted, if I remember right. http://www.globalsign.net/ Rennie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: 30. maj 2007 12:21 To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista unknown publisher Ah ok thank you, what tools can be used to automaticly sign our installer with a certificate? We are looking into buying one from verisign or simular but we are not sure whichever is better and what lets us do this automaticly. Thanks From: Rob Mensching [EMAIL PROTECTED] To: Pseudonymic Wannabe [EMAIL PROTECTED],wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Vista unknown publisher Date: Tue, 29 May 2007 08:47:12 -0700 Sign your MSI. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: Tuesday, May 29, 2007 6:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Vista unknown publisher When running our MSI package on Vista midway under the installation a dialog pops up (UAC) and complains about Unknown Publisher on our package.MSI file and asks for permission to continue. Is there anyway to author our package in such a way that the user won't be bothered with such interference? _ Like the way Microsoft Office Outlook works? You'll love Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-usocid=TXT _TAGHM_mig ration_HM_mini_outlook_0507 _ More photos, more messages, more storage-get 2GB with Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-usocid=TXT_ TAGHM_migration_HM_mini_2G_0507 --- -- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista unknown publisher [OT]
For WinQual you MUST use Verisign but, it's a special certificate which only costs $99 and only works for WinQual authentication. I think you could buy a full Verisign certificate which would work for both WinQual and code signing but, it's still cheaper to buy the $99 winqual and a full certificate from someone else. -Original Message- From: Martin Cetkovsky [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 30, 2007 11:32 AM To: 'Trevor Clifton'; John Vottero; wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: RE: [WiX-users] Vista unknown publisher [OT] Hi, a little bit OT, but interesting for me. Do I understand it well, that for establishing an account for winqual, I can use a certificate from other companies than Verisign as well? Just that the winqual documentation and registration wizard is written in must have Verisign... :/ Thanks, Martin -Original Message- From: [EMAIL PROTECTED] [mailto:wix- [EMAIL PROTECTED] On Behalf Of Trevor Clifton Sent: Wednesday, May 30, 2007 4:50 PM To: 'John Vottero'; wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Vista unknown publisher We had been with VeriSign but they upped their prices again this year so we shopped around. We bought our Class 3 from C.O.M.O.D.O. We have successfully used them to sign all our software (exe's), installers (msi's) and driver packages (cab's) that we upload to Microsoft for digital driver signing. http://www.instantssl.com/code-signing/code-signing.html Only $179 for a full year. Microsoft offers a Deal directly from VeriSign for the Authenticode Digital ID, but it is $399. That is not a deal considering these other competitors exist and offer identical features and services. https://winqual.microsoft.com/help/default.htm#obtaining_a_v erisign_class_3_ digital_id.htm So, choose whomever you wish, but we found that paying more didn't get you anything extra. -Trevor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Vottero Sent: Wednesday, May 30, 2007 7:47 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista unknown publisher I've just been looking at buying a cert and I'm wondering why Verisign is so expensive. Why would someone pay 2 or 3 times more? Is there any difference between what you get from Verisign, Thawte or GlobalSign? -Original Message- From: [EMAIL PROTECTED] [mailto:wix- users- [EMAIL PROTECTED] On Behalf Of Rennie Petersen Sent: Wednesday, May 30, 2007 7:43 AM To: Pseudonymic Wannabe; [EMAIL PROTECTED]; wix- [EMAIL PROTECTED] Subject: Re: [WiX-users] Vista unknown publisher I bought a digital certificate from GlobalSign a couple of months ago. It cost approx. 1/3 what Verisign wanted, if I remember right. http://www.globalsign.net/ Rennie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: 30. maj 2007 12:21 To: [EMAIL PROTECTED]; wix- [EMAIL PROTECTED] Subject: Re: [WiX-users] Vista unknown publisher Ah ok thank you, what tools can be used to automaticly sign our installer with a certificate? We are looking into buying one from verisign or simular but we are not sure whichever is better and what lets us do this automaticly. Thanks From: Rob Mensching [EMAIL PROTECTED] To: Pseudonymic Wannabe [EMAIL PROTECTED],wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Vista unknown publisher Date: Tue, 29 May 2007 08:47:12 -0700 Sign your MSI. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: Tuesday, May 29, 2007 6:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Vista unknown publisher When running our MSI package on Vista midway under the installation a dialog pops up (UAC) and complains about Unknown Publisher on our package.MSI file and asks for permission to continue. Is there anyway to author our package in such a way that the user won't be bothered with such interference? ___ __ Like the way Microsoft Office Outlook works? You'll love Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en- usocid=TXT _TAGHM_mig ration_HM_mini_outlook_0507 _ More photos, more messages, more storage-get 2GB with Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en- usocid=TXT_ TAGHM_migration_HM_mini_2G_0507
Re: [WiX-users] Permission Element, and next v3 pre-release build?
Weekly builds are at: http://wix.sourceforge.net/releases/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lewis G. Pringle, Jr. Sent: Monday, April 30, 2007 10:07 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Permission Element, and next v3 pre-release build? Folks: I've just tried WIX, after a decade of suffering with Installshield, and I'm truly impressed! This is a major improvement! I'm using the latest WIX v3 pre-release build 3.0.2420.0. One of the few (blocking) bugs I've run into appears to be a known bug with handling the Permission element under registry entries. http://sourceforge.net/tracker/index.php?func=detailaid=1560158group_i d=105970atid=642714 According to this link, it was actually fixed in January of 2007. Since the last release (3.0.2420.0) was at the end of 2006, I don't yet have this fix. I was wondering, when is the next planned 'build' of the v3 series to be made available? Is there some way I can get the pre-pre-release builds from CVS, and build the latest version myself (or is it too unstable to make that worthwhile?) Thanks, Lewis. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automating MSI merge into bootstrapper?
You can use IExpress.exe to do that. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas B Sent: Tuesday, April 24, 2007 5:14 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Automating MSI merge into bootstrapper? Hi What would be a nice way to have the MSI merged into the bootstrapper unifying it into just one setup.exe file and nothing more? Can this be done with a buildproject just like creating the bootstrapper? - Thomas - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action works under WinXP-SP2, fails under Win2K?
You do not use privMsiGetPropertyStr to initialize cchIniName. You
initialize cchIniName like this:
char *cchIniName = new char[szBuf];
which just allocates a buffer. The contents of that buffer are
undefined.
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Julie Campbell
Sent: Tuesday, April 24, 2007 4:28 PM
To: 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action works under WinXP-SP2, fails
under Win2K?
No, cchIniName is initialized, I was just saving everyone an extra
chunk of
code that is working. Here is the function that initializes
cchIniName
and
the other WiX property strings before the call to fopen_s:
// NOTE: Caller responsible for freeing TCHAR * buffer if non-null
return
code
TCHAR * __stdcall privMsiGetPropertyStr(MSIHANDLE hInstaller, TCHAR
*strName)
{
TCHAR* szValueBuf = NULL;
DWORD cchValueBuf = 0;
UINT uiStat = ::MsiGetProperty(hInstaller, strName, TEXT(),
cchValueBuf);
if (ERROR_MORE_DATA == uiStat)
{
++cchValueBuf; // output count does not include terminating null, so
add 1
szValueBuf = new TCHAR[cchValueBuf];
if (szValueBuf)
{
uiStat = MsiGetProperty(hInstaller, strName, szValueBuf,
cchValueBuf);
}
}
if (ERROR_SUCCESS != uiStat)
{
if (szValueBuf != NULL)
delete [] szValueBuf;
return NULL;
}
return szValueBuf;
}
---
I copied that chunk of code from somewhere, excuse the poor use of
Hungarian
notation.
If you look at what I am writing to this .ini file, you will notice
that
it has nothing to do with what a IniFile deal with. This is a .ini
file
that supplies java startup variable to Eclipse (actually, our
customized
version of Eclipse). Eclipse is very touchy and I am afraid to try a
unicode file since it works with a text file. Heck, I wouldn't need
this CA
at all if Eclipse could figure out %WINDIR% in a path, but it can't.
As I mentioned, this works GREAT under XP. Though this CA was quickly
hacked together and leaves room for improvement, there is nothing
intrinsically wrong with the CA code. It does what it is supposed to
as
long as the directory it is trying to write to exists before it tries
to
write the file to it. There is something wrong with the .msi
sequencing
that is baffling me, as that directory should exist long before it
tries to
execute my custom action.
Julie Campbell
[EMAIL PROTECTED]
-Original Message-
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 24, 2007 4:17 PM
To: 'Julie Campbell'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Custom Action works under WinXP-SP2,fails
under
Win2K?
Your call to fopen_s uses the uninitialised cchIniName buffer as the
path
name to open for writing.
(BTW, misuse of Hungarian notation because this is _not_ a Count of
Characters - use sz or psz for string-terminated-with-zero. If that's
what
you intended, of course.)
You can also edit INI files using the IniFile element which maps to
a
native Windows Installer feature. The type of the Value field is
Formatted,
so you should be able to substitute property values using [] within
the
field data.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Julie
Campbell
Sent: 24 April 2007 21:09
To: 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action works under WinXP-SP2,fails
under
Win2K?
fprintf writes to the file pointed to by cchIniName.
Julie Campbell
[EMAIL PROTECTED]
-Original Message-
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 24, 2007 4:05 PM
To: 'Julie Campbell'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Custom Action works under WinXP-SP2, fails
under
Win2K?
Did you miss a line out? You don't appear to have written to the
buffer
pointed to by cchIniName so it will be filled with garbage. The
success
or
failure may depend on whether the junk in the buffer parses as a valid
file
name or not.
I would strongly recommend using Unicode file name buffers and
therefore
_wfopen_s if you're targetting Windows NT-based operating systems only
and
not supporting Windows 9X.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Julie
Campbell
Sent: 24 April 2007 20:43
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Action works under WinXP-SP2, fails under
Win2K?
My installer needs to work under WinXP and Win2K for this round. I
wrote a
custom action and it works great under WinXP but fails under Win2K and
I
cannot figure out why. I am using WiX v3.0.2420, both machines have
Windows
R Installer. V 3.01.4000.1823 installed.
The custom action is in a C++ DLL, here is the action function:
UINT __stdcall WriteTSBIni(MSIHANDLE hInstaller)
{
UINTrc =
Re: [WiX-users] Remove a section using XmlFile
In the ElementPath, you misspelled diagnostics. On 4/23/07, Kevin Burton [EMAIL PROTECTED] wrote: My XmlConfig does not seem to work. It doesn't delete the section or the whole node. I don't get a warning or an error. Just what was supposed to be deleted is not. This is the XmlConfig line that I am using: XmlConfig Id=ConsoleAppConfig14 Action =delete ElementPath='//configuration/system.dignostics' File=[CONSOLEINSTALLDIR]app.Config Node=element On=install Sequence =14 VerifyPath='New' / - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using .NET 2.0 Managed Custom Actions
Have you found documentation for InstallUtilLib.dll? Did Microsoft add it to the list of redistributable software? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Friday, April 20, 2007 12:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using .NET 2.0 Managed Custom Actions Congratulations - you reinvented InstallUtilLib.dll... Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mailinglist Sent: Friday, April 20, 2007 4:52 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using .NET 2.0 Managed Custom Actions Hello WiX-users, because we needed to use managed custom actions in our setup, I searched around the net for a real solution to this. I found two projects ([1],[2]), that followed quite good ideas, but both did not work out of the box or only under special circumstances. So I combined them both to something working. Simply, we now use a custom action to start a C++ library, that hosts the CLR, loads a specified assembly and calls a class that needs to implement a small interface. From inside that class the installer context can be used to fill properties, etc. Since the demo code package is 3 MB, I uploaded it to Rapidshare [3] as well as to my blog [4]. Greetings, Oliver Friedrich Consultant - Software Solutions [1] Hosting the CLR within a custom action - Pablo M. Cibaro - http://weblogs.asp.net/cibrax/archive/2005/04/11/399839.aspx [2] Wrapping the Windows Installer 2.0 API - http://www.codeproject.com/csharp/msiinterop.asp [3] Rapidshare Download Link: http://rapidshare.com/files/26953203/ManagedCustomActions.zip.html [4] Blogentry: http://www.forestwalk.de/?p=31 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where to install samples
Microsoft puts lots of samples in Program Files From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Quinton Tormanen Sent: Thursday, April 19, 2007 12:26 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Where to install samples I have a .NET assembly that we've built for use by our customers. We have just added a bunch of sample projects using our assembly that can be also be installed. I'm unclear on where to install these samples. I thought of putting them under [PersonalFolder]\RMCLink Samples, but the negatives soon occurred to me (poor behavior under multiple users), and it was apparent that Orca agreed with me. So, I'm thinking of just putting them in a sub-folder under our install folder (typically C:\Program Files\RMCLink). However, I'm not sure how much Microsoft would like that since to use the samples, the user needs to muck around in C:\Program Files, which doesn't seem like the best place to advice users to browse around. Any thoughts on where the proper place is for such samples? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista certification : InstallLocation in uninstall registry (ARPINSTALLLOCATION )
You need a custom action to set ARPINSTALLLOCATION, something like:
CustomAction
Id=SAVETARGETDIR
Property=ARPINSTALLLOCATION
Value=[TARGETDIR] /
Make sure you schedule that custom action after InstallValidate.
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of William Levra-Juillet
Sent: Thursday, April 19, 2007 10:43 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Vista certification : InstallLocation in
uninstall
registry (ARPINSTALLLOCATION )
Hi,
I'm in the process of getting (at least trying to get) the Vista
Certification.
It required the value InstallLocation to be set by the MSi installer
in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{MyProductGUID
}
But Wix (v3) doesn't seem to properly set this value (set to empty).
If you have any idea on how to set it (automatically by Wix or by a
CA), thx
to help me !
Apparently, according to MSDN it's related to ARPINSTALLLOCATION
property,
but it's not very meanningfull to me...
Thank you very much for your help
Regards
William
---
--
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where to install samples
You might want to consider installing a ZIP file instead of an MSI. That way, people can take a look at the contents, extract single files or extract everything. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Cardiff Sent: Thursday, April 19, 2007 12:30 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Where to install samples Quinton, As richard said I referred to the product's installer that Patterns and Practices provides: Enterprise Library, Smart Client Software Factory, Web Client Software Factory, etc. And with doesn't register the product I mean, Suppress: RegisterProduct, RegisterUser, PublishProduct, PublishFeatures. So the installer don't leave trace of that. On 4/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quinton, If you haven't encountered it, Microsoft's Patterns and Practices group provides a great set of resources. The entry point for all the information is (assuming I still have the right shortcut in my browser favorites) http://msdn2.microsoft.com/en-us/practices/default.aspx Since I can't see any specific information about installing samples I assume Brian is referring to the way the samples available from that site are packaged. Hope this helps. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Quinton Tormanen Sent: Thursday, April 19, 2007 11:55 AM To: Brian Cardiff Cc: John Vottero; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Where to install samples That sounds like a complete way to go. When you say samples.msi doesn't register the product, do this mean that it can't really be uninstalled or repaired - it's just a fire-and-forget install. I'm not clear on what all the necessary steps would be from a standard install that I'm accustomed to doing to make it behave in this fashion. I think that for my project, I'll stick putting them in Program Files for now; it's one less step for the user. The shortcut suggested by Richard makes it much more palatable to me. Also, what are you referring to by Microsoft Patterns Practices? Is there a specific public document that outlines this? Thanks! --Quinton * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. -- Brian J. Cardiff - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IAssemblyCacheItem Commit failed with 0x80131047
You misspelled Community in the LongName.
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Colin Bowern
Sent: Thursday, April 12, 2007 5:17 PM
To: [EMAIL PROTECTED]
Subject: Re: [WiX-users] IAssemblyCacheItem Commit failed with
0x80131047
I haven't solved this yet but I do have a working MSI if I use the
Visual Studio Setup Project. I have compared the MsiAssembly and
MsiAssemblyName tables and there is nothing that stands out.
We are trying to move away from the VS setup project, so I'm hoping
staying with that isn't the answer. :)
-Original Message-
From: Colin Bowern
Sent: Tuesday, April 10, 2007 3:01 PM
To: '[EMAIL PROTECTED]'
Subject: IAssemblyCacheItem Commit failed with 0x80131047
I'm trying to debug a setup project where I have defined a component
with a strongly named assembly:
--snip--
Directory Id=INSTALLDIR_GAC Name=GAC
Component Id=Assemblies_GAC Guid=D50D93D8-B5EF-46f4-A304-
869ADBA389F9
File Id=OfficialCommuntiy.Common.dll_GAC Name=occgac.dll
LongName=OfficialCommuntiy.Common.dll DiskId=1
Source=C:\Projects\Common\trunk\Common\bin\Release\OfficialCommunity.C
ommon.dll KeyPath=yes Assembly=.net /
/Component
/Directory
--snip--
I am able to GAC the assembly using GacUtil on the command line, the
dependencies are already in the GAC as well. Reflector shows the
assembly full name as:
OfficialCommunity.Common, Version=2.2.0.0, Culture=neutral,
PublicKeyToken=9c02f6b549e26545
In the msiexec.log I'm seeing the following to which I have researched
with no real conclusion:
--snip--
MSI (s) (B0:9C) [14:21:05:060]: Assembly Error:The given assembly name
or codebase, '%1', was invalid.
MSI (s) (B0:9C) [14:21:05:060]: Note: 1: 1935 2: {D50D93D8-B5EF-46F4-
A304-869ADBA389F9} 3: 0x80131047 4: IAssemblyCacheItem 5: Commit 6:
OfficialCommunity.Common,version=2.2.0.0,culture=neutral,publicKeyT
oken=9C02F6B549E26545,processorArchitecture=MSIL
Error 1935. An error occurred during the installation of assembly
'OfficialCommunity.Common,version=2.2.0.0,culture=neutral,publicKey
Token=9C02F6B549E26545,processorArchitecture=MSIL'. Please refer
to
Help and Support for more information. HRESULT: 0x80131047. assembly
interface: IAssemblyCacheItem, function: Commit, component: {D50D93D8-
B5EF-46F4-A304-869ADBA389F9}
MSI (s) (B0:9C) [14:21:21:916]: Product: Common Framework 2.2 CTP --
Error 1935. An error occurred during the installation of assembly
'OfficialCommunity.Common,version=2.2.0.0,culture=neutral,publicKey
Token=9C02F6B549E26545,processorArchitecture=MSIL'. Please refer
to
Help and Support for more information. HRESULT: 0x80131047. assembly
interface: IAssemblyCacheItem, function: Commit, component: {D50D93D8-
B5EF-46F4-A304-869ADBA389F9}
--snip--
Part of the difficultly is the relative undocumented nature of
IAssemblyCacheItem. The assembly name looks correct. I'm assuming
the
processorArchitecture attribute gets tacked on and should be alright?
I have tried adding the ProcessorArchitecture attribute to the File
element and it did not make a difference.
Any thoughts on other potential causes or knowledge of resolutions?
Thanks!
Colin
---
--
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVD
EV
___
WiX-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing .NET Services
I would use the WiX ServiceInstall. It's easier and more reliable than trying to call the Installer class. You can leave the Installer based class in the code if you want. From: Don Tasanasanta [mailto:[EMAIL PROTECTED] Sent: Friday, April 06, 2007 3:00 PM To: John Vottero; Kevin Burton; Rob Mensching; BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Installing .NET Services So what is the correct way to handle situations like this? Let's say there's a .net service that needs installing but has Installer based classes. How should the install handle this? From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Thursday, April 05, 2007 9:57 AM To: Kevin Burton; Don Tasanasanta; Rob Mensching; BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Installing .NET Services Correct. Neither WiX's ServiceInstall nor SC CREATE need or use the Installer class. But, they can both install .NET based services whether the service has an Installer based class or not. From: Kevin Burton [mailto:[EMAIL PROTECTED] Sent: Thursday, April 05, 2007 12:54 PM To: John Vottero; 'Don Tasanasanta'; 'Rob Mensching'; 'BULL, Dave, GBM'; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Installing .NET Services The problem is that none if the Installer methods or events are getting called. With InstallUtil the methods and events associated with the Installer base class are call. With ServiceInstall they are not. I would assume that SC_CREATE would also not call the Installer base class methods. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Vottero Sent: Thursday, April 05, 2007 11:41 AM To: Don Tasanasanta; Rob Mensching; BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing .NET Services I don't think there's a difference between installing a .NET service vs . a regular service so, ServiceInstall doesn't need to detect anything. Can you install your service with SC CREATE? The InstallUtil.exe doesn't know a service from a hole in the ground. All it does is look for classes that have the RunInstaller attribute and it calls the right methods (depending on the command line switches). Was your service already installed the first time that you tried to install it via WiX? I'm not sure what Windows Installer does if a service is already installed when it thinks it's installing for the first time. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta Sent: Thursday, April 05, 2007 12:28 PM To: Rob Mensching; BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing .NET Services How does ServiceInstall detect that you're installing a .net service as opposed to a regular service? I'm experiencing difficulties installing a .net service using ServiceInstall. The service is there but doesn't seem to be registering properly. How does ServiceInstall work compared to the .net utility InstallUtil.exe? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, October 25, 2006 8:12 AM To: BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing .NET Services ServiceInstall should just work. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BULL, Dave, GBM Sent: Wednesday, October 25, 2006 5:52 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing .NET Services Hi Wix people I am having problems installing a windows service written in .NET. I am using wix 3.0.2128.0. I have successfully managed to install services written in unmanaged C++ using the ServiceInstall tag, but this doesn't seem to work for my .NET component. Do I have to use the method which is mentioned here: http://installneo.blogspot.com/2004/09/installing-windows-services-creat ed.html ? ... or should the ServiceInstall tag work? Dave *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely
Re: [WiX-users] Installing .NET Services
I don't think there's a difference between installing a .NET service vs . a regular service so, ServiceInstall doesn't need to detect anything. Can you install your service with SC CREATE? The InstallUtil.exe doesn't know a service from a hole in the ground. All it does is look for classes that have the RunInstaller attribute and it calls the right methods (depending on the command line switches). Was your service already installed the first time that you tried to install it via WiX? I'm not sure what Windows Installer does if a service is already installed when it thinks it's installing for the first time. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta Sent: Thursday, April 05, 2007 12:28 PM To: Rob Mensching; BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing .NET Services How does ServiceInstall detect that you're installing a .net service as opposed to a regular service? I'm experiencing difficulties installing a .net service using ServiceInstall. The service is there but doesn't seem to be registering properly. How does ServiceInstall work compared to the .net utility InstallUtil.exe? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, October 25, 2006 8:12 AM To: BULL, Dave, GBM; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing .NET Services ServiceInstall should just work. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BULL, Dave, GBM Sent: Wednesday, October 25, 2006 5:52 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing .NET Services Hi Wix people I am having problems installing a windows service written in .NET. I am using wix 3.0.2128.0. I have successfully managed to install services written in unmanaged C++ using the ServiceInstall tag, but this doesn't seem to work for my .NET component. Do I have to use the method which is mentioned here: http://installneo.blogspot.com/2004/09/installing-windows-services-creat ed.html ? ... or should the ServiceInstall tag work? Dave *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbos.com http://www.rbsmarkets.com *** - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET Installer class and Wix/Msi interaction.
The short answer is, you can't do it. Visual Studio uses InstallUtilLib.dll which is an MSI custom action that installs Installer based classes. As far as I know, it's not documented and not redistributable. Someone did reverse engineer InstallUtilLib and they wrote a blog post about how to get it working, you could try searching for that. That still won't fix the not redistributable part. You may need to figure out what the performance counter installer class really does and do it yourself. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton Sent: Tuesday, April 03, 2007 5:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] .NET Installer class and Wix/Msi interaction. I want to add some performance counters to my .NET Windows Service. There is a performance class installer but I am not sure how this class derived from the Installer class interacts with the Wix/Msi installation process. Anyone able to shed some light on this? Thank you. Kevin - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET Installer class and Wix/Msi interaction.
I've never written or installed performance counters so, I'm not sure I can help much. You might want to take a look at the PerfCounter WiX element. I think it's for unmanaged perf counters but, I could be wrong. You could also look into what the managed installer class is really doing. For example, the PowerShell SnapIn Installer class is for registering a PowerShell SnapIn but, it just creates some registry entries so the WiX Registry element works just fine. From: Kevin Burton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 6:36 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] .NET Installer class and Wix/Msi interaction. I am sorry to hear that but now I know. Thank you. If I do it on my own how do I let MSI/Wix know about the installed performance counters so they will be uninstalled with the application uninstall? From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 5:13 PM To: Kevin Burton; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] .NET Installer class and Wix/Msi interaction. The short answer is, you can't do it. Visual Studio uses InstallUtilLib.dll which is an MSI custom action that installs Installer based classes. As far as I know, it's not documented and not redistributable. Someone did reverse engineer InstallUtilLib and they wrote a blog post about how to get it working, you could try searching for that. That still won't fix the not redistributable part. You may need to figure out what the performance counter installer class really does and do it yourself. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton Sent: Tuesday, April 03, 2007 5:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] .NET Installer class and Wix/Msi interaction. I want to add some performance counters to my .NET Windows Service. There is a performance class installer but I am not sure how this class derived from the Installer class interacts with the Wix/Msi installation process. Anyone able to shed some light on this? Thank you. Kevin - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] problem when run custom action before costinitialize
Wait=Yes means wait up to 30 seconds for the service to enter a STOPPED state rather than a STOP_PENDING state. In our case, our service would report STOPPED very quickly but, the process would still be running up to 90 seconds later because it was waiting for an I/O to complete that would never complete. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Friday, March 30, 2007 12:42 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] problem when run custom action before costinitialize ...and the point of that Wait=Yes is that it translates to Wait=1 in the ServiceControl table so that it does really wait for the Service to finish, not just for the SCM to respond. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Vottero Sent: Thursday, March 29, 2007 7:32 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] problem when run custom action before costinitialize You could have a race condition (we did). I don't know if it's Windows Installer or a WiX Custom Action that stops services but, it appears that it continues when the service controller reports that the service is stopped. The service controller reports a service as stopped when the service successfully responds to a stop request (i.e. a ServiceBase based class' OnStop method completes successfully). But, the files are in-use until the process exits. If your OnStop method just starts the shutdown and then returns, you have a problem. Your OnStop method should start the shutdown of the service threads and then wait for them to complete before it exits. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 5:54 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] problem when run custom action before costinitialize I did that, Component... File ... Name=MyService.exe /File ServiceControl Id=MyService Name=MyService.exe Stop=uninstall Remove=uninstall Wait=yes ServiceArgument /d [INSTALLDIR]EF.G/ServiceArgument /ServiceControl /Component I still get file-in-use popup when uninstall.(Stop service is happened after CostFinilize, InstallValidate) From: Rob Mensching Sent: Thursday, March 29, 2007 2:41 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize You should be able to just schedule the service to be stopped and no file-in-use error should occur. From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 2:11 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, --- -- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVD EV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future
Re: [WiX-users] problem when run custom action before costinitialize
You could have a race condition (we did). I don't know if it's Windows Installer or a WiX Custom Action that stops services but, it appears that it continues when the service controller reports that the service is stopped. The service controller reports a service as stopped when the service successfully responds to a stop request (i.e. a ServiceBase based class' OnStop method completes successfully). But, the files are in-use until the process exits. If your OnStop method just starts the shutdown and then returns, you have a problem. Your OnStop method should start the shutdown of the service threads and then wait for them to complete before it exits. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 5:54 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] problem when run custom action before costinitialize I did that, Component... File ... Name=MyService.exe /File ServiceControl Id=MyService Name=MyService.exe Stop=uninstall Remove=uninstall Wait=yes ServiceArgument /d [INSTALLDIR]EF.G/ServiceArgument /ServiceControl /Component I still get file-in-use popup when uninstall.(Stop service is happened after CostFinilize, InstallValidate) From: Rob Mensching Sent: Thursday, March 29, 2007 2:41 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize You should be able to just schedule the service to be stopped and no file-in-use error should occur. From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 2:11 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut pointing toward product name
You’re creating an advertized shortcut (Advertise=”yes”). When you start an
advertised shortcut, Windows checks to see if the component is installed, if it
is, it starts it. If it isn’t, it installs it and then starts it.
You need to change Advertised to “no” and there may be other details that need
to change too.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sawyer, Shane
Sent: Tuesday, March 27, 2007 12:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shortcut pointing toward product name
Sorry, I am using version 3. The spaces aren’t there in my code. Everything
works fine except the target of the shortcut.
thanks
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 9:47 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shortcut pointing toward product name
You didn’t mention which version of WiX you are using.
I am still using version 2, and I have an additional “LongName” attribute on
the shortcut. If you are using version 2 as well (and I suspect you’re not),
you may want to try adding one of those.
I also notice that you seem to have spaces in front of the file ID and Name. I
don’t know if that is a) intentional, b) a gift from your (or my) email
package, or c) a typo. I doubt it’s causing a problem, but you never know!
Regards,
Richard
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sawyer, Shane
Sent: Tuesday, March 27, 2007 11:23 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shortcut pointing toward product name
I am trying to create a desktop shortcut, and its working except that the
shorcut’s target is the Product Name. What am I missing? A google search told
me to add the keypath attribute to the file, but it still doesn’t work. Here
is my wxs code… thanks
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=COMPANYDIR Name=Nelnet
Directory Id=APPLICATIONFOLDER Name=Navigator
Component Id=MainExecutable
Guid={2539F193-BAD7-4fe0-A2C0-D5027EB5BAB4}
File Id= Ice.Client.Navigator.exe Name=
Ice.Client.Navigator.exe DiskId=1 Source=C:\Builds\ICE\QA\Intelligent
Customer Engagement\Ice.Client.Navigator.exe Vital=yes KeyPath=yes
Shortcut Id=DesktopShortcut
Directory=DesktopFolder Name=Navigator Advertise=yes Icon=Icon.ico
WorkingDirectory=APPLICATIONFOLDER /
/File
/Component
/Directory
/Directory
/Directory
Directory Id=DesktopFolder Name=. SourceName=Desktop /
/Directory
Feature Id=MainExecFeature Title=Navigator Executable Level=1
ComponentRef Id=MainExecutable /
/Feature
Property Id=ApplicationFolderName Value=Navigator /
Property Id=ALLUSERS1/Property
Icon Id=Icon.ico
SourceFile=C:\Builds\ICE\Install\Navigator\icon.ico /
* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the individual or
entity to whom it is addressed. If you have received this communication in
error, be aware that forwarding it, copying it, or in any way disclosing its
content to any other person, is strictly prohibited. Peek Traffic Corporation
is neither liable for the contents, nor for the proper, complete and timely
transmission of (the information contained in) this communication. If you have
received this communication in error, please notify the author by replying to
this e-mail immediately and delete the material from any computer.
The information
contained in this message is confidential proprietary property of Nelnet, Inc.
and its affiliated companies (Nelnet) and is intended for the recipient only.
Any reproduction, forwarding, or copying without the express permission of
Nelnet is strictly prohibited. If you have received this communication in
error, please notify us immediately by replying to this e-mail.
The information
contained in this message is confidential proprietary property of Nelnet, Inc.
and its affiliated companies (Nelnet) and is intended for the recipient only.
Any reproduction, forwarding, or copying without the express permission of
Nelnet is strictly prohibited. If you have received this communication in
error, please notify us immediately by replying to this e-mail.
Re: [WiX-users] Wix votive stable version
I think you're looking in the wrong place. You said There is no add as link option shown on my system when I right click the project on my my system. Add shows New Item Existing Item and Folder. Add as link doesn't show up when you right click the project. You right-click the project, pick Add - Existing item. A dialog box will open where you can select the item to add and, the Add button in that dialog box is a pulldown menu that includes Add as link and Add. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Wieser Sent: Tuesday, March 27, 2007 12:24 PM To: Chris Bardon; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix votive stable version Can you, or anyone else for that matter, insert a link to another project, as Justin described here: Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive In Visual Studio, when you select Add Existing File... if you just click Add, then the file will be copied to your local directory. This is by design and works the same way as C#, VB, etc. If you want to add a link, which you do, then drop down the little arrow next to the Add you'll see an Add As Link option. You want to select that. This will then populate your MSBuild (.wixproj) file for you correctly. You will not be allowed to Delete that file, but you can remove the link from your project. Does this make sense? There is no add as link option shown on my system when I right click the project on my my system. Add shows New Item Existing Item and Folder. Am I looking in the wrong place? Anthony Wieser Wieser Software Ltd - Original Message - From: Chris Bardon mailto:[EMAIL PROTECTED] To: Nitin Chaudhari mailto:[EMAIL PROTECTED] ; wix-users@lists.sourceforge.net Sent: Tuesday, March 27, 2007 3:20 PM Subject: Re: [WiX-users] Wix votive stable version So far, I've been using the Votive 3.0 build without any problems. I think the only thing unstable about the build is that there could be breaking changes in future releases that mean you'll have to change your code. Other than the environment variable macros (being able to refer to project output) not being in the 3.0 build, it seems to be much fuller featured than 2.0. Chris - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do I remove a file on upgrade
I think you're breaking the component rules. You put PlaneDisaster.exe and PlaneDisaster.Dba.dll in the same component which you really don't want to do. I don't think you ever want more than one executable file in a component. In most cases, you only want one file in each component. If PlaneDisaster.lib.dll was in its own component, you could change the name and the component id and Windows Installer would install the new component and remove the old component. One of the rules for when you need to change the component code is: A change in the name or target location of any file, registry key, shortcut, or other resource in the component. In this case, you must also change the name or target location of every resource in the component. That is from: http://msdn2.microsoft.com/en-us/library/aa367849.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Justin Dearing Sent: Sunday, March 25, 2007 11:17 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How do I remove a file on upgrade Hello, I am having a problem in that I renamed a DLL in my open source project (http://plane-disaster.sf.net) and it is not being removed when I perform an upgrade. The old version of the file is called PlaneDisaster.LIB.dll and the new version is called PlaneDisaster.Dba.dll. I just made the DLL name match the namespace. When I perform an uninstall both DLLs are removed. The diff of Setup.wxs after the file rename is below. How do I remove PlaneDisaster.LIB.dll if I upgrade from pre version 0.93 to version 0.93 (or later). Index: C:/SRC/PlaneDisaster.NET/PlaneDisaster.NET Setup/Setup.wxs === --- C:/SRC/PlaneDisaster.NET/PlaneDisaster.NET Setup/Setup.wxs (revision 48) +++ C:/SRC/PlaneDisaster.NET/PlaneDisaster.NET Setup/Setup.wxs (revision 53) @@ -7,8 +7,8 @@ -- Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product - Id=942fbc80-9e58-4436-aa7c-5e40c4f95ce7 - Name=PlaneDisaster.NET 0.9.2 + Id=5725e292-d33f-11db-8314-0800200c9a66 + Name=PlaneDisaster.NET 0.9.3 Language=1033 Codepage=1252 Version=0.9.2 @@ -16,7 +16,7 @@ Manufacturer=ZippySoft Package - Id=E77100E0-6CE2-40DE-BE21-BB4C76C1CA80 + Id=63bc6e90-d33f-11db-8314-0800200c9a66 Description=#Description Comments=Comments InstallerVersion=200 --- -- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVD EV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# .dll
The situation is clearly broken and it's up to Microsoft to fix it. John Vottero So, John, why don't you go complain to Microsoft and more specifically the Windows Installer team? I know there are a number of us on the mailing list that work for Microsoft and we really do try to help where possible but you have to understand that quite often customers (especially a group of them) get more attention than internal employees. Ok, what's the best way to send my concerns to the Windows Installer team? I was searching for a way to contact the Windows Installer team and ran across this: http://blogs.msdn.com/heaths/archive/2007/03/14/introducing-windows-inst aller-powershell-extensions.aspx on Heath Stewart's blog. The part that made me laugh was: There is no installation package yet as I explore better alternatives to running installutil.exe or implementing similar functionality for use in an in-process custom action I hope Heath is part of the Windows Installer team! Complaining here will educate those of us on the WiX toolset (I'm always happy to listen) and I try to roll up the major pain points I get here to the Windows Installer team. However, I still often end up being counted as one voice. If you want change then you need to go to the people that you believe need changing. We've been quite clear here that the goal of the WiX toolset is support everything the Windows Installer supports. Until we get the nod from the Windows Installer that managed code is an okay thing to do we really can't support it in the WiX toolset. Therefore, all we can do with you here is commiserate but that won't fix what you want fixed. I understand the situation that WiX is in. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# .dll
Bob Arnson wrote: John Vottero wrote: The System.Configuration.Installer base class has virtual methods for Install, Uninstall, Commit and Rollback. Doesn't that mean that that it can support Rollbacks? Yes, they can. The number that do is vanishingly small. Doing it right is hard, regardless of language. Half the time, they're not even close to necessary: The event log stuff in InstallUtil, for example, just writes registry keys. So you have CAs and managed CAs when a few rows in the Registry table get it for free. I agree that writing a good CA is hard but, I'll bet it's easier in C# than it is in C. I also agree that eliminating a CA is the best way to make it robust. The PowerShell stuff is also just a bunch of registry entries (I think, it's not documented). I don't know enough about Windows Installer to understand all the implications of managed CAs. What I do know is that there are many groups at Microsoft that are creating managed CAs to support their products and they aren't creating unmanaged CAs and they aren't documenting what their managed CAs actually do so ISV's are left stuck in the middle. We have to reverse engineer the Microsoft managed CAs so we can develop proper installers. The situation is clearly broken and it's up to Microsoft to fix it. Yes and in addition to Rob's suggestion of pinging the MSI team, I'll add: Ping the teams whose stuff you use. Let them know that blindly calling managed code via InstallUtil isn't good enough for you. Teams like the black-box approach because it gives them future flexibility (over, say, documenting the registry entries their IntallUtil CAs write). Tough. Let them know it. Document the stuff and WiX can handle them via extensions and, when necessary, CAs. I always try to register my concerns with the teams producing the managed installers. The PowerShell team has said that they would document what their managed installer does but, I haven't seen the documentation yet. The future flexibility angle is my biggest worry. One of these days, some team is going to completely scramble what their managed installer does and they'll think that they aren't breaking anything. If they really want that future flexibility, they have to put some pressure on the Windows Installer team to support managed Installers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registry keys and component rules
This is really more of a Windows Installer question than a WiX questions but, I'm not getting any responses in the msi newsgroup. The component rules make it pretty clear that you can't add or remove a registry key without creating a new component. Do they really mean registry key? Can I add or remove registry *entries* without breaking the component rules? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# .dll
On Sat, 24 Mar 2007 20:38:16 +, Fredrik Grohn wrote: First to all, please, clear out all the participants from the To: and CC: lines and keep the discussion on the list itself. I guess we all monitor it regularly so it's really not beneficial to receive every posting twice, both directly and from the list. Fredrik, What I don't understand is why people are so eager to build managed custom actions in the first place. That's what bothers me, too. If somebody really wanting to write a managed (or unmanaged) custom action could tell us why he or she needs it in the first place. I completely agree with Richard Foster, me, too: the only real custom action I ever wrote was to check the product key entered by the user. I have a suspicion that the need for custom actions stem from sloppy programming of the application to be installed rather than any real, legitimate need for something WI can't solve. The ONLY reason that I have for using a managed custom action is that *Microsoft* is telling me to. Last year, I went to an ISV training course presented by Microsoft at Microsoft and the MMC and PowerShell teams both showed us how to create managed Installer based classes to install our MMC and PowerShell snapins. When I asked them about this problem, they didn't seem to understand the issue. More and more managed Installer based classes are being released by Microsoft and in most cases, they aren't documenting what the installers do. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] run a script passing a parameter
Here's how we call CAQuietExec twice: CustomAction Id=SetCreateDB Property=CreateDB Value=quot;[#JAMSDBAEXE]quot; INSTALL/ CustomAction Id=SetLoadDB Property=LoadDB Value=quot;[#JAMSDBAEXE]quot; LOAD/ Property Id=QtExecCmdTimeout Value=600/ CustomAction Id=CreateDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ CustomAction Id=LoadDB BinaryKey=wixca DllEntry=CAQuietExec Execute=deferred Impersonate=yes Return=check/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dave_c Sent: Thursday, February 22, 2007 11:47 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] run a script passing a parameter I'm guessing I am mis-understanding what you are telling me because if I change my code to read Binary Id=wixca src=c:\wix_v2_orig\wixca.dll/ Property Id=QtExecCmdLine Value=quot;perlquot; quot;[INSTALLDIR]first.plquot; install/ CustomAction Id=QtExec BinaryKey=wixca DllEntry=CAQuietExec Execute=immediate Return=check/ InstallExecuteSequence Custom Action=QtExec After=InstallFinalizeNOT Installed/Custom /InstallExecuteSequence Property Id=QtExecCmdLine Value=quot;perlquot; quot;[INSTALLDIR]first.plquot; deinstall/ CustomAction Id=QtExecu BinaryKey=wixca DllEntry=CAQuietExec Execute=immediate Return=check/ InstallExecuteSequence Custom Action=QtExecu After=InstallFinalizeInstalled AND NOT REINSTALL/Custom /InstallExecuteSequence I get an error message during compilation saying, not un-reasonably 'Duplicate Symbol QtExecCmdLine found' Could you explain more or better show what I shuld have done in the snippet of code shown. Bob Arnson-3 wrote: dave_c wrote: Property Id=QtExecInstall Value='perl [INSTALLDIR]first.pl install'/ CustomAction Id=QtExec BinaryKey=wixca DllEntry=CAQuietExec Execute=immediate Return=check/ QuietExec requires the same QtExecCmdLine property to be set each time it's called. You'll need custom actions to set the property before each call to CAQuietExec. -- sig://boB http://bobs.org -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/run-a-script-passing-a-parameter-tf32721 81.html#a9103524 Sent from the wix-users mailing list archive at Nabble.com. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforge CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Prevent MSI to be invoked directly
We use Wix and the MSBuild GenerateBootstrapper too. We use IExpress.exe to to combine everything into a single executable. IExpress is part of IE so, you probably already have it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ricardo Lopes Sent: Wednesday, February 21, 2007 5:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Prevent MSI to be invoked directly Hi, I made a MSI installer using Wix and a bootstrapper using the msbuild GenerateBootstrapper task, it creates a setup.exe and a msi file, but the msi can be invoke directly overcoming the checks made by the bootstrapper and there are checks on the bootstrapper that are difficult to include as conditions to prevent the installer from running. Is there any way to do any of this : - avoid the msi from unless is started by the bootstrapper (some kind of condition) - merge the bootstrapper and the msi in only one file and start the setup.exe when the merged file is started. - any other suggestion ? I tried to change the extension of the msi to .dat and start that file from the setup.exe but it doesn't work as i expected. Thanks, Ricardo Lopes. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] automatically launching .Net framework install if it (.Net framework) is not present
Look up GenerateBootstrapper Task in the Visual Studio 2005 documentation index. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 17, 2007 6:59 PM To: Sotorin Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] automatically launching .Net framework install if it (.Net framework) is not present Bob had earlier suggested the Visual Studio bootstrapper. I have not found decent documentation for it. Perhaps I did not look at the right places. I had already started writing my own little bootstrapper in un-managed C++ that looks in the registry to find if the .Net framework is installed Root='HKLM' Key='Software\Microsoft\.NETFramework\Policy\v2.0' Name='50727' and if it is not, launches Microsoft Component installer (download the SDK from the follwoing link) http://www.microsoft.com/downloads/details.aspx?familyid=2A5E4EBC-651C-4 0AA-9525-1810AF47C317displaylang=en configured to install the .Net framework and the windows installer (as required) followed by my application installer. You could of course just configure the above to do the whole thing but like I said in my original email, the user experience is not so good when the framework (all prerequisites that the component installer installs) are already installed because the first dialog the install program puts up is the Finish installation dialog before launching your app's install. If you manage to use the Visual Studio bootstrapper it might be useful to post the info here for other users. If you write your own bootstrapper in C/C++ using VS 2005, remember to statically link the C/C++ runtime (this is not the default anymore) Sandeep Sotorin [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/17/2007 03:33 PM To wix-users@lists.sourceforge.net cc Subject Re: [WiX-users] automatically launching .Net framework install if it (.Net framework) is not present Ok, then how can you do it? I can package distributable on the same CD, I can detect if it's installed on user's computer but how can you trigger automatic install? Installing Framework (if it's not installed) is mandatory task we have to perform with our installer. Mike Dimmick-2 wrote: As Bob said, you cannot do this because you can't have two MSI installations running concurrently. The .NET Framework 2.0 installation will fail if you try to run it from a custom action in your MSI. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sotorin Sent: 17 January 2007 20:49 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] automatically launching .Net framework install if it (.Net framework) is not present You can download donetfx.exe (which is Framework 2.0 redistributable) and run it from your MSI via CustomAction's ExeCommand attirbute. CustomAction ExeCommand=[INSTALLDIR]dotnetfx.exe .. / This is exactly what I have to do too. Bob Arnson-3 wrote: [EMAIL PROTECTED] wrote: However I want my setup to launch Microsoft Component installer SDK or .Net framewrok installer to automatically install the .Net framework if needed. You can't do that from your .msi because .NET is installed via MSI and you can't have two MSIs running simultaneously. The current Visual Studio bootstrapper has been discussed on this list recently and seems to be the leading favorite for bootstrappers ready to use. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/automatically-launching-.Net-framework-install-if- it-%28.Net-framework%29-is-not-present-tf3023754.html#a8422126 Sent from the wix-users
Re: [WiX-users] zip program for bootstrapper msi
Ok, I looked into the details because this is working for us. We use IExpress to compress everything into a single executable. You probably already have IExpress, I believe that it's part of IE. IExpress lets you specify a setup command (AppLaunched) and a post install command (PostInstallCmd). We run the MSBuild/GenerateBootstrapper with AppLaunched and we run our bootstrapper/installer with the PostInstallCmd. The things I don't like about IExpress are: - Command line support is weak - You can't change the executable's Icon - You can't change the executable's tooltip description - You can't change the executable's version From: David Thielen [mailto:[EMAIL PROTECTED] Sent: Friday, December 15, 2006 1:18 PM To: John Vottero; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] zip program for bootstrapper msi The only problem is it's Microsoft's bootstrapper from MSBuild/GenerateBootstrapper so I have no control over that. Thanks - dave David Thielen www.windwardreports.com 303-499-2544 x1185 Cubicle Wars - http://www.windwardreports.com/film.htm From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Friday, December 15, 2006 8:19 AM To: David Thielen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] zip program for bootstrapper msi I don't think your bootstrapper should exit until the msi is done installing. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Friday, December 15, 2006 2:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] zip program for bootstrapper msi Hi; Can anyone suggest one to use to unzip the 2 files and then launch the bootstrapper? * Winzip won't work because it deletes the unzipped file as soon as the first exists - so the msi will be deleted when the bootstrapper completes and spawns it. * Chilkat doesn't run will in a build script (file is still locked when it returns, can't set the caption or icon). ??? - thanks - dave David Thielen www.windwardreports.com 303-499-2544 x1185 Cubicle Wars - http://www.windwardreports.com/film.htm - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is click once what we should be using?
I think you should look at the GenerateBootstrapper MSBuild task. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Tuesday, December 05, 2006 10:19 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is click once what we should be using? Hi; We have a WIX built installer that works great. And we are working on creating a bootstrapper for the prerequisites that would call our msi at the end to complete the install. Should we be looking at click once? thanks - dave - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready?
I've asked many times for people to send me information that their company uses the WiX toolset to build their MSI packages so I can post it on the web site. Nobody has been willing to send in their name. We use WiX to build our msi packages and we're willing to have our company and/or product name on the WiX web site. Let me know if what you need (if anything). John Vottero MVP Systems, Inc. http://www.mvpsi.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Rockwood Sent: Monday, November 06, 2006 17:26 To: [EMAIL PROTECTED]; 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready? 1. Good idea. We should probably do that on our home page. 2. I can get to wix.sourceforge.net just fine. Maybe SourceForge was down for a minute? If you keep having problems getting to it, let us know. Justin -Original Message- From: Jacek Blaszczynski [mailto:[EMAIL PROTECTED] Sent: Monday, November 06, 2006 5:23 PM To: 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready? Hello Justin! Thnx for this list of references it is really very helpfull to me. Personally I am not worried for WiX stability or robustness and I used it for all my installation packages created during last year. Furthermore, I am a strong advocate of WiX among all my customers. However, I would strongly recommend to fix 2 small things which create problems for coders trying to convince their customers to use WiX: 1. Provide official list of most prominent installer packages created with WiX - it tells actually everything. 2. Provide nice WiX home page linked via sourceforge.net project page - currently wix.sourceforge.net points to nothing and it may be bad www card for the package. Jacek -Original Message- From: Justin Rockwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 1:16 AM To: [EMAIL PROTECTED]; 'Mike Dimmick'; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready? Here are some of the Microsoft products and groups that use WiX for their installations: * Office 2007 * Office Server 2007 * Windows SharePoint Server * SQL Server 2005 * Visual Studio * Windows Defender Additionally, there are several non-Microsoft products that use WiX. The biggest one that comes to mind is MySQL. There are lots more, but I can't remember off the top of my head. WiX has become the de-facto installation technology within Microsoft and all of the major product groups use it for their installations. If you or your client are worried about the stability, robustness, etc. don't be. The fact that some of the largest software products in the world use WiX should be testament enough that it's enterprise ready. Now, having said that, it doesn't mean that WiX is complete by any means. There is still lots of active development that goes on in the 3.0 version (which is still beta). Also, although there's a Visual Studio development experience, Votive still lacks a lot of the nice GUI designers that you'll find in Wise or InstallShield. There are some 3rd party designers for WiX files also available. And yes, sadly our documentation is not up to snuff yet. Let us know if you have any other questions. Justin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Blaszczynski Sent: Monday, November 06, 2006 2:58 PM To: 'Mike Dimmick'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready? Hello! Thnx for replies - they are very helpful. Can someone from MSFT WiX developers confirm which enterprise grade product installers are currently created with help of WiX package? Rgrds Jacek -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Monday, November 06, 2006 9:48 PM To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready? I know that Microsoft use WiX for at least some parts of the SQL Server 2005, Office 2007 and Exchange Server 2007 installers. Version 2.0.x is considered the stable version. It does get bugfixes, but no major new development. Version 3.0.x is considered the unstable development version. The versions at http://sourceforge.net/project/showfiles.php?group_id=105970 of both are considered particularly stable; there are point releases (approximately weekly) at http://wix.sourceforge.net/releases/ (when it works). Most people want to download the binaries or the Votive MSI, not the sources
Re: [WiX-users] Votive V3 and multiple .msi support?
You can't build two executables with one project, why would that be different with setups? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Friedrich, Oliver Sent: Thursday, November 16, 2006 6:21 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive V3 and multiple .msi support? Well, thought so. Would not anyone think it should be possible to build to .msi's with one Project? With such an Scenario, one could work with paths (e.g. to include-files) that would not need to go out of the projects scope. Just a quick thought... thx, Oliver From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 11:45 PM To: Friedrich, Oliver; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Votive V3 and multiple .msi support? I would imagine that you would need two projects, one for each package. You can have both projects in the same solution. However, some versions of Visual Studio misbehave if you have multiple projects with the same output directory (though that may just apply to C# or VB). I would recommend using the same Fragments for the main body of your installation to ensure that you're not making component errors. If a resource (such as a file) is installed to the same location by two different components (identified by component GUID), Bad Things can happen. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Friedrich, Oliver Sent: 15 November 2006 10:38 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Votive V3 and multiple .msi support? Hello again, Using Votive V3 is pretty nice, though one thing is a little bit anoying... For our Solution we need to build 2 packages, one for the client and one for the server application. Those packages use pretty much the same code, thats why they are in one Solution of VS2005. Now, much WiX-code could be shared between those to packages, too. So i thought it would be enough, do add another .wxs file to the Votive V3 project, to get it build a second .msi, but that does not work, Votive complains about double entry points. Is it possible, to share WiX-code for two Setups in one Votive Solution? I have at least 10 files, that are used by both setup scripts. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
