Re: [WiX-users] Creating patches
Hello, I am still looking for an answer to this problem. I have two versions of my MSI installer, the only true difference is the version number. I have a patch.wxs script which identitifies a couple of components which are supposedly changed. In reality no file have been changed, except for their version number. When I execute the tools sequence described in Nick Ramirez' book and the WiX manual, nothing constructive happens. Both Torch and Pyro gives me errors, shown below. I am pretty much clueless as to what I am doing wrong, mainly because neither the manual or the book properly explains WHAT I need to do, and WHY. Mainly they just show me HOW. Is any able to help get past this issue? /Thomas Due > -Original Message- > From: Thomas Due [mailto:t...@scanvaegt.dk] > Sent: 3. maj 2013 09:40 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Creating patches > > I have now modified my build script to use a locally build msi installer and > comparing it with a version build on my build server yesterday. > There is no practical difference between the two msi files except the version > numbers. > > Is that why I keep getting errors? > > I get the following error from Torch: > error TRCH0279 : The table definition of 'WixVariable' in the target database > does not match the table definition in the updated database. A transform > requires that the target database schema match the updated database > schema. > > And I get this from Pyro: > Updating file information. > Creating cabinet files. > There will be '8' threads used to produce CAB files. > MinorUpdate\Patch.wxs(13) : warning PYRO1079 : The cabinet Patch.cab' > does not contain any files. If this patch contains no files, this warning can > likely be safely ignored. Otherwise, try passing -p to torch.exe when first > building the transforms, or add a ComponentRef to your PatchFamily > authoring to pull changed files into the cabinet. > Creating cabinet 'AppData\Local\Temp\q0qw3fj2\#Patch.cab'. > Generating database. > pyro.exe : error PYRO0001 : Cannot set column 'Protocol' with value 1 > because it is less than the minimum allowed value for this column, 6. > > Exception Type: System.InvalidOperationException > > Stack Trace: >at > Microsoft.Tools.WindowsInstallerXml.ColumnDefinition.ValidateValue(Objec > t value) >at Microsoft.Tools.WindowsInstallerXml.Row.set_Item(Int32 field, Object > value) >at Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output > transform, String transformFile) >at Microsoft.Tools.WindowsInstallerXml.Binder.GenerateDatabase(Output > output, String databaseFile, Boolean keepAddedColumns, Boolean > useSubdirectory) >at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output > output, String databaseFile) >at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String > file) >at Microsoft.Tools.WindowsInstallerXml.Tools.Pyro.Run(String[] args) > > Any help will be appreciated. > > /Thomas Due > > > > -Original Message- > > From: uni [mailto:unigauld...@gmail.com] > > Sent: 2. maj 2013 12:07 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Creating patches > > > > 于02 May 2013 17:31:10,Thomas Due写到: > > > Hello, > > > > > > I am trying to grasp the concept of minor and small upgrades, but I > > > am > > having some trouble with getting it to work. > > > > > > First of all, it doesn't seem to work at all with 3.7. > > > I have downgraded my WiX to 3.5, and there something happens at > > > least, > > but my msp seems to be empty when I examine it with instead > > (http://www.instedit.com/). > > > > > > A bit about what I do: > > > I have a fairly complex installer with a couple of hundred files > > > total, divided > > among 4 features. I build this with TeamCity, and I have two separate > > installers (no real changes, except for the version nummer - > > 1.2.0.22679 and 1.2.5.22754). I imagine that this should be enough to > generate something. > > > > > > I have a build script, a simple batch file, which executes the four > > > steps > > described in both the WiX doc and Nick Ramirez' book. > > > > > > My patch.wxs then includes a couple of file components, as I want > > > these > > replaces (mind you, I am still in the testing phase, trying to > > understand the concept). > > > > > > First my "build script": > > > === > > > "%wixdir%bin\torch.exe" -p -xi %oldmsi% %newmsi% -v -out diff.wixmst > > > "%wixdir%bin\candle.exe" -v Patch.wxs "%wixdir%bin\Light.exe" -v > > > Patch.wixobj -out patch.wixmsp "%wixdir%bin\pyro.exe" -v > > > "patch.wixmsp -out patch.msp -t Patch diff.wixmst > > > > > > %oldmsi% and %newmsi" are complete paths to the wixpdb files for > > respectively old and new installer. > > > Then my Patch.wsx: > > > === > > > > > xmlns="http://schemas.microsoft.com/wix/2006/w
[WiX-users] Executing SQL in WIX
Hi, Am trying to execute a .sql file using the sqlscript during the uninstall and not during install. find the snippet below Can any one help me. Thanks and Regards Ravi -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file
Your messages seemed to indicate that the custom action was a black box to you and/or that you didn't have access to the source. You use ORCA to stream the foo.ca.dll out of the binary table and then you use winzip to extract the custom action assembly, the interop library and anything else that you packaged into the custom action dll.Redgate is then used to decompile it back into source so you can find the session.Log() entry that was logging your secrets. So you have the source and you found it. Great. Now you know how to do it the other way if you ever need to one day. From: "Jeremiahf" Sent: Monday, May 06, 2013 10:38 PM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file Chris, Winzip? Its an MSI. Why use Redgate when I have the source to the CA? No offense, I guess I just don't understand your response. I FINALLY FOUND THE LINE OF CODE that was passing the connection string to the log and commented it out. Rob was absolutely correct. It WAS the CA logging the parameters! I was stuck on looking at HideTarget and Hidden at the time in the WIX code... NOTE! Take a break from the screen! Thank you everyone for all your help!! Cheers! Jeremiah On Mon, May 6, 2013 at 3:11 PM, Christopher Painter wrote: Except when they are called by a ControlEvent. :-) It looks to me that the C#/DTF custom action has some initialization to called session.Log(). This would be easy enough to tell by using WinZip to extract the assembly from the self extract custom action ( foo.dll from foo.ca.dll ) and then decompile it using a program like RedGate Reflector. From: "Phil Wilson" Sent: Monday, May 06, 2013 12:40 PM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file ...and at the risk of stating the obvious, custom actions can put messages in the MSI log by calling MsiProcessMessage(). That's a good thing of course, except when it gives away secrets ;) Phil -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: Monday, May 06, 2013 10:22 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file Well it's not "their" CA, it's DTF, so they or I can't answer the question directly, but it just seems that DTF is logging the connection string, however it gets it. Phil -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, May 06, 2013 9:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file Are they setting a property within their CA called ConnectionString? -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: Monday, May 06, 2013 11:48 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file In context, that full log entry was previously posted as: === Action start 17:26:56: InstallFinalize. SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI1045.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action DatabaseCA!DatabaseCA.CustomActions.DatabaseCA Begin DatabaseCA Connecton String: Data Source=source;Packet Size=4096;Uid=sqluser;Pwd=mypassword = Whicc is DTF doing the logging, methinks. Jeremiahf didn't show all the data in that recent reply, so without the SFXCA prefix it is misleading. Phil -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: Monday, May 06, 2013 8:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file Hi Rob, I'm pretty certain it is the installer logging what the custom action is doing. I ran the installer in verbose mode and noticed the password and server parameters were not being displayed in plain text. MSI (c) (A8:F8) [09:58:01:363]: Command Line: USERNAME=sa PASSWORD=** SERVER=** Then when my custom action is called it is logging sql connection string in plain text. Begin DatabaseCA Connecton String: Data Source=source;Packet Size=4096;Uid=sqluser;Pwd= mypassword J On Sat, May 4, 2013 at 1:49 AM, Rob Mensching wrote: > Is the message showing the password actually being logged by the > custom action itself? > > > On Fri, May 3, 2013 at 3:53 PM, Jeremiahf wrote: > > > Steven, > > > > "Tried adding: HideTarget="yes" that didn't help" Indeed! > > > > I'm even tried to remove logging from the custom action and I still > > see > the > > password... > > I've even checked MsiHidden
[WiX-users] Regd MsiDriverPackages flag
Hi all, I need to dynamically change MsiDriverPackages flag in wix for forcing an installation based on some condition. How to do that with difx:driver tag? -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file
I see what you are saying. Sorry if my messages were not clear. Thank you Chris for your feedback. J On Tue, May 7, 2013 at 8:14 AM, Christopher Painter wrote: > Your messages seemed to indicate that the custom action was a black box to > you and/or that you didn't have access to the source. You use ORCA to > stream the foo.ca.dll out of the binary table and then you use winzip to > extract the custom action assembly, the interop library and anything else > that you packaged into the custom action dll.Redgate is then used to > decompile it back into source so you can find the session.Log() entry that > was logging your secrets. > > So you have the source and you found it. Great. Now you know how to do > it the other way if you ever need to one day. > -- > *From*: "Jeremiahf" > *Sent*: Monday, May 06, 2013 10:38 PM > *To*: chr...@iswix.com, "General discussion for Windows Installer XML > toolset." > > *Subject*: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log > file > > > Chris, > > Winzip? Its an MSI. Why use Redgate when I have the source to the CA? > No offense, I guess I just don't understand your response. > > I FINALLY FOUND THE LINE OF CODE that was passing the connection string > to the log and commented it out. Rob was absolutely correct. It WAS the CA > logging the parameters! I was stuck on looking at HideTarget and Hidden at > the time in the WIX code... NOTE! Take a break from the screen! Thank you > everyone for all your help!! > > Cheers! > > Jeremiah > > > On Mon, May 6, 2013 at 3:11 PM, Christopher Painter wrote: > >> >> >> Except when they are called by a ControlEvent. :-) >> >> It looks to me that the C#/DTF custom action has some initialization to >> called session.Log(). This would be easy enough to tell by using WinZip >> to extract the assembly from the self extract custom action ( foo.dll from >> foo.ca.dll ) and then decompile it using a program like RedGate >> Reflector. >> >> >> From: "Phil Wilson" >> Sent: Monday, May 06, 2013 12:40 PM >> To: "General discussion for Windows Installer XML toolset." >> >> Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log >> file >> >> ...and at the risk of stating the obvious, custom actions can put >> messages >> in the MSI log by calling MsiProcessMessage(). That's a good thing of >> course, except when it gives away secrets ;) >> >> Phil >> >> -Original Message- >> From: Phil Wilson [mailto:phil.wil...@mvps.org] >> Sent: Monday, May 06, 2013 10:22 AM >> To: 'General discussion for Windows Installer XML toolset.' >> Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log >> file >> >> Well it's not "their" CA, it's DTF, so they or I can't answer the >> question >> directly, but it just seems that DTF is logging the connection string, >> however it gets it. >> >> Phil >> >> -Original Message- >> From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] >> Sent: Monday, May 06, 2013 9:56 AM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log >> file >> >> Are they setting a property within their CA called ConnectionString? >> >> -Original Message- >> From: Phil Wilson [mailto:phil.wil...@mvps.org] >> Sent: Monday, May 06, 2013 11:48 AM >> To: 'General discussion for Windows Installer XML toolset.' >> Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log >> file >> >> In context, that full log entry was previously posted as: >> === >> Action start 17:26:56: InstallFinalize. >> SFXCA: Extracting custom action to temporary directory: >> C:\WINDOWS\Installer\MSI1045.tmp-\ >> SFXCA: Binding to CLR version v2.0.50727 Calling custom action >> DatabaseCA!DatabaseCA.CustomActions.DatabaseCA >> >> Begin DatabaseCA >> >> Connecton String: Data Source=source;Packet >> Size=4096;Uid=sqluser;Pwd=mypassword >> = >> >> Whicc is DTF doing the logging, methinks. Jeremiahf didn't show all the >> data >> in that recent reply, so without the SFXCA prefix it is misleading. >> >> Phil >> >> -Original Message- >> From: Jeremiahf [mailto:jeremi...@gmail.com] >> Sent: Monday, May 06, 2013 8:08 AM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log >> file >> >> Hi Rob, >> >> I'm pretty certain it is the installer logging what the custom action is >> doing. I ran the installer in verbose mode and noticed the password and >> server parameters were not being displayed in plain text. >> MSI (c) (A8:F8) [09:58:01:363]: Command Line: USERNAME=sa >> PASSWORD=** SERVER=** >> Then when my custom action is called it is logging sql connection string >> in >> plain text. >> Begin DatabaseCA >> Connecton String: Data Source=sou
Re: [WiX-users] Bundle Package Install Failure
Hi Jeremiah. I appreciate your replies.
Turns out the client was able to install after rebooting and logging in as the
local administrator. According to client, were previously using a domain
account that's in the Administrators group and using run as admin to launch
setup. Not sure why that should not have worked. The log below seems to
confirm that setup was launched elevated. I'm guessing perhaps a group policy
kicking in only with a domain login(?).
> Date: Mon, 6 May 2013 10:36:18 -0500
> From: jeremi...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bundle Package Install Failure
>
> Sorry, it was a very long day.
>
> Have you tried running the installer as administrator?
>
>
> On Sat, May 4, 2013 at 1:25 AM, - Arzola - wrote:
>
> > Yes. As seen below, the installer is detecting that the required .net
> > framework 4.0 is already present with no need to install.
> >
> > [063C:11BC][2013-05-03T19:00:12]i201: Planned package:
> > NetFx40ClientRedist, state: Present, default requested: Present, ba
> > requested: Present, execute: None, rollback: None, cache: No, uncache: No,
> > dependency: None
> > > CC: wix-users@lists.sourceforge.net
> > > From: jeremi...@gmail.com
> > > Date: Fri, 3 May 2013 22:51:15 -0500
> > > To: wix-users@lists.sourceforge.net
> > > Subject: Re: [WiX-users] Bundle Package Install Failure
> > >
> > > Do you have the correct version of .net installed?
> > >
> > >
> > >
> > > On May 3, 2013, at 7:43 PM, - Arzola - wrote:
> > >
> > > > Hello,One of our clients is encountering a setup failure with the
> > following msg: '0X80070002 - The system cannot find the file
> > specified.'The log file is below. The install scope is perMachine. Any
> > ideas on why it would be failing when trying to cache the bundle? This is
> > the first time we've encountered this after many successful installations
> > and is rather urgent. Any insight would be greatly appreciated...
> > [063C:11BC][2013-05-03T19:00:08]i001: Burn v3.7.1224.0, Windows v6.1
> > (Build 7601: Service Pack 1), path:
> > C:\Systems\Product_1\Product_1\Setup.exe, cmdline: '-burn.unelevated
> > BurnPipe.{1DE19E8A-81A6-4AA5-BF48-70A9F6456F73}
> > {6B32BA48-178D-44AA-B502-0EE1BD74773C} 716'
> > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > 'WixBundleLog' to value
> > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008.log'
> > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > 'WixBundleOriginalSource' to value
> > 'C:\Systems\Product_1\Product_1\Setup.exe'
> > > > [063C:11BC][2013-05-03T19:00:08]i052: Condition '((VersionNT >= v5.1)
> > AND (ServicePackLevel >= 3)) OR ((VersionNT >= v5.2) AND (ServicePackLevel
> > >= 2)) OR (VersionNT >= v6.0)' evaluates to true.
> > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > 'WixBundleName' to value 'ProductName'
> > > > [063C:11BC][2013-05-03T19:00:09]i100: Detect begin, 5 packages
> > > > [063C:11BC][2013-05-03T19:00:09]i000: Setting string variable
> > 'NETFRAMEWORK40CLIENT' to value '1'
> > > > [063C:11BC][2013-05-03T19:00:09]i052: Condition 'NETFRAMEWORK40CLIENT'
> > evaluates to true.
> > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > NetFx40ClientRedist, state: Present, cached: None
> > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: Drivers64bit,
> > state: Absent, cached: None
> > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: Drivers32bit,
> > state: Absent, cached: None
> > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App64bit,
> > state: Absent, cached: None
> > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App32bit,
> > state: Absent, cached: None
> > > > [063C:11BC][2013-05-03T19:00:09]i199: Detect complete, result: 0x0
> > > > [063C:11BC][2013-05-03T19:00:12]i200: Plan begin, 5 packages, action:
> > Install
> > > > [063C:11BC][2013-05-03T19:00:12]w321: Skipping dependency registration
> > on package with no dependency providers: NetFx40ClientRedist
> > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'VersionNT64'
> > evaluates to true.
> > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > 'WixBundleRollbackLog_Drivers64bit' to value
> > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_0_Drivers64bit_rollback.log'
> > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > 'WixBundleLog_Drivers64bit' to value
> > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_0_Drivers64bit.log'
> > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'NOT VersionNT64'
> > evaluates to false.
> > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'VersionNT64'
> > evaluates to true.
> > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > 'WixBundleRollbackLog_App64bit' to value
> > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_1_App64bit_rollback.log'
> > > > [063C:11BC][2013-05-03T19:00:12]i000
Re: [WiX-users] Bundle Package Install Failure
I'd be curious to know what happened if the client just launched the
install without using "Run As Admin" to launch setup. "Run As Admin" can do
funny things to the profile the launched process sees so I'm wondering if
there is something weird that Burn needs to handle.
On Tue, May 7, 2013 at 8:59 AM, - Arzola - wrote:
> Hi Jeremiah. I appreciate your replies.
> Turns out the client was able to install after rebooting and logging in as
> the local administrator. According to client, were previously using a
> domain account that's in the Administrators group and using run as admin to
> launch setup. Not sure why that should not have worked. The log below
> seems to confirm that setup was launched elevated. I'm guessing perhaps a
> group policy kicking in only with a domain login(?).
> > Date: Mon, 6 May 2013 10:36:18 -0500
> > From: jeremi...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bundle Package Install Failure
> >
> > Sorry, it was a very long day.
> >
> > Have you tried running the installer as administrator?
> >
> >
> > On Sat, May 4, 2013 at 1:25 AM, - Arzola -
> wrote:
> >
> > > Yes. As seen below, the installer is detecting that the required .net
> > > framework 4.0 is already present with no need to install.
> > >
> > > [063C:11BC][2013-05-03T19:00:12]i201: Planned package:
> > > NetFx40ClientRedist, state: Present, default requested: Present, ba
> > > requested: Present, execute: None, rollback: None, cache: No, uncache:
> No,
> > > dependency: None
> > > > CC: wix-users@lists.sourceforge.net
> > > > From: jeremi...@gmail.com
> > > > Date: Fri, 3 May 2013 22:51:15 -0500
> > > > To: wix-users@lists.sourceforge.net
> > > > Subject: Re: [WiX-users] Bundle Package Install Failure
> > > >
> > > > Do you have the correct version of .net installed?
> > > >
> > > >
> > > >
> > > > On May 3, 2013, at 7:43 PM, - Arzola -
> wrote:
> > > >
> > > > > Hello,One of our clients is encountering a setup failure with the
> > > following msg: '0X80070002 - The system cannot find the file
> > > specified.'The log file is below. The install scope is perMachine. Any
> > > ideas on why it would be failing when trying to cache the bundle?
> This is
> > > the first time we've encountered this after many successful
> installations
> > > and is rather urgent. Any insight would be greatly appreciated...
> > > [063C:11BC][2013-05-03T19:00:08]i001: Burn v3.7.1224.0, Windows v6.1
> > > (Build 7601: Service Pack 1), path:
> > > C:\Systems\Product_1\Product_1\Setup.exe, cmdline: '-burn.unelevated
> > > BurnPipe.{1DE19E8A-81A6-4AA5-BF48-70A9F6456F73}
> > > {6B32BA48-178D-44AA-B502-0EE1BD74773C} 716'
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleLog' to value
> > > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008.log'
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleOriginalSource' to value
> > > 'C:\Systems\Product_1\Product_1\Setup.exe'
> > > > > [063C:11BC][2013-05-03T19:00:08]i052: Condition '((VersionNT >=
> v5.1)
> > > AND (ServicePackLevel >= 3)) OR ((VersionNT >= v5.2) AND
> (ServicePackLevel
> > > >= 2)) OR (VersionNT >= v6.0)' evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleName' to value 'ProductName'
> > > > > [063C:11BC][2013-05-03T19:00:09]i100: Detect begin, 5 packages
> > > > > [063C:11BC][2013-05-03T19:00:09]i000: Setting string variable
> > > 'NETFRAMEWORK40CLIENT' to value '1'
> > > > > [063C:11BC][2013-05-03T19:00:09]i052: Condition
> 'NETFRAMEWORK40CLIENT'
> > > evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > > NetFx40ClientRedist, state: Present, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> Drivers64bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> Drivers32bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App64bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App32bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i199: Detect complete, result: 0x0
> > > > > [063C:11BC][2013-05-03T19:00:12]i200: Plan begin, 5 packages,
> action:
> > > Install
> > > > > [063C:11BC][2013-05-03T19:00:12]w321: Skipping dependency
> registration
> > > on package with no dependency providers: NetFx40ClientRedist
> > > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'VersionNT64'
> > > evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > > 'WixBundleRollbackLog_Drivers64bit' to value
> > >
> 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_0_Drivers64bit_rollback.log'
> > > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > > 'WixBundleLog_Drivers64bit' to value
> > >
> 'C:\User
[WiX-users] Custom BA or not?
What are the general rules for writing a custom BA or not? I have the custom BA installing v4 already and do some code to figure out if other requirements are there. If I can customize a UI through Wix (and use to capture parameters) what do I really need a BA for? Are there some good rules of thumb to use? David White Chief Software Engineer Living PlanIT SA Mobile: 586-354-5996 (c) Living PlanIT SA This electronic message contains privileged and confidential information and is intended for the use of the addressee only. Any dissemination, access, copying, disclosure, use or redistribution of this message or any of its contents by anyone without prior permission of the sender is strictly prohibited. If you have received this message in error, please delete it and notify the sender by reply. We disclaim all responsibility and cannot accept liability for the consequences of any person acting, or refraining from acting on the contents of the message and the information contained in this email can in no way be considered legally binding. Views presented in this message are solely the responsibility of the author and are not necessarily those of Living PlanIT SA. -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle Package Install Failure
Hello,
The funny thing is that it crossed my mind. "Rebooting fixes everything"
ha! Glad to hear it worked out for you.
J
On Tue, May 7, 2013 at 10:59 AM, - Arzola - wrote:
> Hi Jeremiah. I appreciate your replies.
> Turns out the client was able to install after rebooting and logging in as
> the local administrator. According to client, were previously using a
> domain account that's in the Administrators group and using run as admin to
> launch setup. Not sure why that should not have worked. The log below
> seems to confirm that setup was launched elevated. I'm guessing perhaps a
> group policy kicking in only with a domain login(?).
> > Date: Mon, 6 May 2013 10:36:18 -0500
> > From: jeremi...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Bundle Package Install Failure
> >
> > Sorry, it was a very long day.
> >
> > Have you tried running the installer as administrator?
> >
> >
> > On Sat, May 4, 2013 at 1:25 AM, - Arzola -
> wrote:
> >
> > > Yes. As seen below, the installer is detecting that the required .net
> > > framework 4.0 is already present with no need to install.
> > >
> > > [063C:11BC][2013-05-03T19:00:12]i201: Planned package:
> > > NetFx40ClientRedist, state: Present, default requested: Present, ba
> > > requested: Present, execute: None, rollback: None, cache: No, uncache:
> No,
> > > dependency: None
> > > > CC: wix-users@lists.sourceforge.net
> > > > From: jeremi...@gmail.com
> > > > Date: Fri, 3 May 2013 22:51:15 -0500
> > > > To: wix-users@lists.sourceforge.net
> > > > Subject: Re: [WiX-users] Bundle Package Install Failure
> > > >
> > > > Do you have the correct version of .net installed?
> > > >
> > > >
> > > >
> > > > On May 3, 2013, at 7:43 PM, - Arzola -
> wrote:
> > > >
> > > > > Hello,One of our clients is encountering a setup failure with the
> > > following msg: '0X80070002 - The system cannot find the file
> > > specified.'The log file is below. The install scope is perMachine. Any
> > > ideas on why it would be failing when trying to cache the bundle?
> This is
> > > the first time we've encountered this after many successful
> installations
> > > and is rather urgent. Any insight would be greatly appreciated...
> > > [063C:11BC][2013-05-03T19:00:08]i001: Burn v3.7.1224.0, Windows v6.1
> > > (Build 7601: Service Pack 1), path:
> > > C:\Systems\Product_1\Product_1\Setup.exe, cmdline: '-burn.unelevated
> > > BurnPipe.{1DE19E8A-81A6-4AA5-BF48-70A9F6456F73}
> > > {6B32BA48-178D-44AA-B502-0EE1BD74773C} 716'
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleLog' to value
> > > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008.log'
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleOriginalSource' to value
> > > 'C:\Systems\Product_1\Product_1\Setup.exe'
> > > > > [063C:11BC][2013-05-03T19:00:08]i052: Condition '((VersionNT >=
> v5.1)
> > > AND (ServicePackLevel >= 3)) OR ((VersionNT >= v5.2) AND
> (ServicePackLevel
> > > >= 2)) OR (VersionNT >= v6.0)' evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > 'WixBundleName' to value 'ProductName'
> > > > > [063C:11BC][2013-05-03T19:00:09]i100: Detect begin, 5 packages
> > > > > [063C:11BC][2013-05-03T19:00:09]i000: Setting string variable
> > > 'NETFRAMEWORK40CLIENT' to value '1'
> > > > > [063C:11BC][2013-05-03T19:00:09]i052: Condition
> 'NETFRAMEWORK40CLIENT'
> > > evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > > NetFx40ClientRedist, state: Present, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> Drivers64bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> Drivers32bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App64bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App32bit,
> > > state: Absent, cached: None
> > > > > [063C:11BC][2013-05-03T19:00:09]i199: Detect complete, result: 0x0
> > > > > [063C:11BC][2013-05-03T19:00:12]i200: Plan begin, 5 packages,
> action:
> > > Install
> > > > > [063C:11BC][2013-05-03T19:00:12]w321: Skipping dependency
> registration
> > > on package with no dependency providers: NetFx40ClientRedist
> > > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'VersionNT64'
> > > evaluates to true.
> > > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > > 'WixBundleRollbackLog_Drivers64bit' to value
> > >
> 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_0_Drivers64bit_rollback.log'
> > > > > [063C:11BC][2013-05-03T19:00:12]i000: Setting string variable
> > > 'WixBundleLog_Drivers64bit' to value
> > >
> 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008_0_Drivers64bit.log'
> > > > > [063C:11BC][2013-05-03T19:00:12]i052: Condition 'NOT Version
Re: [WiX-users] Bundle Package Install Failure
Rob, I will try and get feedback from client and post back here.
> From: r...@robmensching.com
> Date: Tue, 7 May 2013 09:05:07 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bundle Package Install Failure
>
> I'd be curious to know what happened if the client just launched the
> install without using "Run As Admin" to launch setup. "Run As Admin" can do
> funny things to the profile the launched process sees so I'm wondering if
> there is something weird that Burn needs to handle.
>
>
> On Tue, May 7, 2013 at 8:59 AM, - Arzola - wrote:
>
> > Hi Jeremiah. I appreciate your replies.
> > Turns out the client was able to install after rebooting and logging in as
> > the local administrator. According to client, were previously using a
> > domain account that's in the Administrators group and using run as admin to
> > launch setup. Not sure why that should not have worked. The log below
> > seems to confirm that setup was launched elevated. I'm guessing perhaps a
> > group policy kicking in only with a domain login(?).
> > > Date: Mon, 6 May 2013 10:36:18 -0500
> > > From: jeremi...@gmail.com
> > > To: wix-users@lists.sourceforge.net
> > > Subject: Re: [WiX-users] Bundle Package Install Failure
> > >
> > > Sorry, it was a very long day.
> > >
> > > Have you tried running the installer as administrator?
> > >
> > >
> > > On Sat, May 4, 2013 at 1:25 AM, - Arzola -
> > wrote:
> > >
> > > > Yes. As seen below, the installer is detecting that the required .net
> > > > framework 4.0 is already present with no need to install.
> > > >
> > > > [063C:11BC][2013-05-03T19:00:12]i201: Planned package:
> > > > NetFx40ClientRedist, state: Present, default requested: Present, ba
> > > > requested: Present, execute: None, rollback: None, cache: No, uncache:
> > No,
> > > > dependency: None
> > > > > CC: wix-users@lists.sourceforge.net
> > > > > From: jeremi...@gmail.com
> > > > > Date: Fri, 3 May 2013 22:51:15 -0500
> > > > > To: wix-users@lists.sourceforge.net
> > > > > Subject: Re: [WiX-users] Bundle Package Install Failure
> > > > >
> > > > > Do you have the correct version of .net installed?
> > > > >
> > > > >
> > > > >
> > > > > On May 3, 2013, at 7:43 PM, - Arzola -
> > wrote:
> > > > >
> > > > > > Hello,One of our clients is encountering a setup failure with the
> > > > following msg: '0X80070002 - The system cannot find the file
> > > > specified.'The log file is below. The install scope is perMachine. Any
> > > > ideas on why it would be failing when trying to cache the bundle?
> > This is
> > > > the first time we've encountered this after many successful
> > installations
> > > > and is rather urgent. Any insight would be greatly appreciated...
> > > > [063C:11BC][2013-05-03T19:00:08]i001: Burn v3.7.1224.0, Windows v6.1
> > > > (Build 7601: Service Pack 1), path:
> > > > C:\Systems\Product_1\Product_1\Setup.exe, cmdline: '-burn.unelevated
> > > > BurnPipe.{1DE19E8A-81A6-4AA5-BF48-70A9F6456F73}
> > > > {6B32BA48-178D-44AA-B502-0EE1BD74773C} 716'
> > > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > > 'WixBundleLog' to value
> > > > 'C:\Users\manager\AppData\Local\Temp\ProductName_20130503190008.log'
> > > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > > 'WixBundleOriginalSource' to value
> > > > 'C:\Systems\Product_1\Product_1\Setup.exe'
> > > > > > [063C:11BC][2013-05-03T19:00:08]i052: Condition '((VersionNT >=
> > v5.1)
> > > > AND (ServicePackLevel >= 3)) OR ((VersionNT >= v5.2) AND
> > (ServicePackLevel
> > > > >= 2)) OR (VersionNT >= v6.0)' evaluates to true.
> > > > > > [063C:11BC][2013-05-03T19:00:08]i000: Setting string variable
> > > > 'WixBundleName' to value 'ProductName'
> > > > > > [063C:11BC][2013-05-03T19:00:09]i100: Detect begin, 5 packages
> > > > > > [063C:11BC][2013-05-03T19:00:09]i000: Setting string variable
> > > > 'NETFRAMEWORK40CLIENT' to value '1'
> > > > > > [063C:11BC][2013-05-03T19:00:09]i052: Condition
> > 'NETFRAMEWORK40CLIENT'
> > > > evaluates to true.
> > > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > > > NetFx40ClientRedist, state: Present, cached: None
> > > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > Drivers64bit,
> > > > state: Absent, cached: None
> > > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package:
> > Drivers32bit,
> > > > state: Absent, cached: None
> > > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App64bit,
> > > > state: Absent, cached: None
> > > > > > [063C:11BC][2013-05-03T19:00:09]i101: Detected package: App32bit,
> > > > state: Absent, cached: None
> > > > > > [063C:11BC][2013-05-03T19:00:09]i199: Detect complete, result: 0x0
> > > > > > [063C:11BC][2013-05-03T19:00:12]i200: Plan begin, 5 packages,
> > action:
> > > > Install
> > > > > > [063C:11BC][2013-05-03T19:00:12]w321: Skipping dependency
> > registration
> > > > on package with no dependency providers: NetFx40ClientRedist
> > > > > > [063C:
[WiX-users] Problem using WIX3.7 for VS2010 & .Net 3.5
Team, We are using VS2010 and targeting to .Net3.5 framework. We are trying to upgrade from WIX3.5 to WIX3.7. After upgrade when we try to compile all wix projects I am getting the following error "'file:///C:\Program Files\WiX Toolset v3.7\bin\candle.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." The work around provided by Rob (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-3-7-Woes-with-VS2008-td7582558.html) is to add the following tag True. Do I need to add this attribute in all my 8 wix projects or is there a place I can add anywhere globally(such as wix.targets or wix200x.targets or wix2010.targets) so that it will work for all wix projects till we update to wix3.8. Please help in regarding this. Regards, Sharan -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Need suggestion on custom feature selection implementation
Hi,
I am developing an installer using WiX 3.7 and want to implement freature
selection dialog to install the feature. I have three of them:
- FEATURE_DEFAULT
- FEATURE_CLASS_A
- FEATURE_CLASS_B
As per name, FEATURE_DEFAULT will always install, FEATURE_CLASS_A and
FEATURE_CLASS_B will get installed on checkbox selection. Here is the code:
1 NOT
CHKBOX_A NOT CHKBOX_B
Things are working fine while installing. But Now I have to attach Add /
Remove feature in the installer. So After MaintenanceDlg, I switch to
FeaturesDlg. Here I see two checkboxes, both unchecked (actually installed
feature checkbox must be checked). Also I want to implement Add feature so
if user want to install a new feature the only this will get installed and
not other feature get touched.
For this I used custom action to control the checkbox property. Code:
foreach (FeatureInfo fi in session.Features)
{
if (fi.Name == "FEATURE_CLASS_A" && fi.CurrentState == InstallState.Local)
{
GetSetProperties.SetSessionProperty(session, "CHECKBOX_ENABLE", "1");
}
}
So if feature is installed previously checkbox gets checked. But if I check
other checkbox, then installer installs both features (which I don't want).
If I uncheck previous checkbox (as I am adding new feature and removing old
one), then previous feature gets removed. I am stuck here.
How can I achieve what I want to do? Is there a better solution for this
(apart from what I am doing)?
Help needed, its really urgent.
--
Thanks and Regards,
Ravi Raj
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file
Phil, You were also absolutely correct!!! Sorry that I missed this email thread. Thank you and everyone for all your help. I'm sorry it took so long. We have been moving projects around so it has been hectic! Thank you again, J On Fri, May 3, 2013 at 10:41 PM, Steven Ogilvie wrote: > Your right Phil, it is a custom action that is creating the connection > string, as per the log below, luckily our connection string is encrypted... > For me, I took out the custom action to set the property and that solved > my issue... (I am using a Publish element in the dialog the sets the > property for Web App Pool password.. > > Sorry J, I don't think you will be able to get rid of it... > > -Original Message- > From: Phil Wilson [mailto:phil.wil...@mvps.org] > Sent: May-03-13 7:20 PM > To: 'General discussion for Windows Installer XML toolset.' > Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log > file > > I'm repeating myself to attempt to make this clear. This appears to be the > part of the log that you are worried about: > = > SFXCA: Extracting custom action to temporary directory: > C:\WINDOWS\Installer\MSI1045.tmp-\ > SFXCA: Binding to CLR version v2.0.50727 Calling custom action > DatabaseCA!DatabaseCA.CustomActions.DatabaseCA > Begin DatabaseCA > Connecton String: Data Source=source;Packet > Size=4096;Uid=sqluser;Pwd=mypassword > == > > This is NOT coming from Windows Installer. The SFXCA (which I believe is > DTF) custom action is logging the connection string that contains the > password. Any discussion of HideTarget is irrelevant as this is not Windows > Installer logging data, it is the custom action code. > > Phil > > > -Original Message- > From: Jeremiahf [mailto:jeremi...@gmail.com] > Sent: Friday, May 03, 2013 3:54 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log > file > > Steven, > > "Tried adding: HideTarget="yes" that didn't help" Indeed! > > I'm even tried to remove logging from the custom action and I still see > the password... > I've even checked MsiHiddenProperties and see that PASSWORD is listed > along with CA_DBAction... Not in SecureCustomProperties... I added > secure="yes" > and now it is there.. Execute the installer with logging and it is still > unsecure in plain text in the log. It must be between the MSI installer and > the SQL connection that is being made. Thoughts? > > J > > > On Fri, May 3, 2013 at 1:48 PM, Steven Ogilvie > wrote: > > > I was not using managed code custom actions... > > > > I was doing: > > > > > > > Property="CA_WebAppPoolPassword." > > Value="WEBAPPPOOL_PASSWORD=[WEBAPPPOOL_PASSWORD]"/> > > Tried adding: HideTarget="yes" that didn't help > > > >> After="CA_DataBasePassword.SetProperty">NOT Installed > > > > This property was in a custom dialog: > > > Y="152" Text="Web App Pool user password:" Transparent="yes" > NoPrefix="yes" > > /> > > > Y="152" Property="WEBAPPPOOL_PASSWORD" Password="yes" TabSkip="no" /> > > > Order="9">1 > > > > It was the custom action " CA_WebAppPoolPassword.SetProperty " that > > was displaying the property in the MSI log file. > > > > Took it out and now the password is not being displayed in plain > letters... > > > > Steve > > > > > > -Original Message- > > From: Phil Wilson [mailto:phil.wil...@mvps.org] > > Sent: May-03-13 2:27 PM > > To: 'General discussion for Windows Installer XML toolset.' > > Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI > > log file > > > > The way it works in MSI isn't really mysterious. Basically the > > property name needs to be public (and that means it must be all > > uppercase). If WiX does its thing properly then you can open the > > generated MSI file with an editor such as Orca, look in the Properties > > table, and in the Property table there'll be a SecureCustomProperties > > property and your property name will be in that list. > > > > This works. If it didn't work then Microsoft would be all over it as a > > security bug. > > > > Generally speaking, people get account passwords from a MSI dialog and > > store it in a property such as MYPASSWORD, and then pass it to a > > custom action that uses it. > > > > However, you're using managed code custom actions, and it seems from > > the log that the (DTF?) code just does its own logging into the MSI > > log without caring whether there's a password in there. So it may be a > > DTF thing, not sure, and if it is then HideTarget etc won't help at > > all. The short answer is that if the DTF code is logging a connection > > string that typically contains a password, then it probably shouldn't. > > > > Phil > > > > -Original Message- > > From: Jeremiahf [mailto:jeremi...@gmail.com] > > Sent: Thursday, May 02, 2013 4:17 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users
[WiX-users] Wix & WCF
Hi All, I have an interesting question for you guys. I am trying to get my custom MBA to consume a WCF service that it installs after it completes. I've successfully imported the service reference to the project, but when the installer runs, it can't seem to find the endpoints in the app.config file. My question is - is the app.config file ignored by burn? If so, it's not the end of the world as I can add the endpoints programmatically, but I would like to know either way. Thanks, Nick -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UNSUBSCRIBE
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] restart logic following a reboot
Here is my scenario: * I've created an install and custom managed bootstrapper based on Wix 3.7 * The install is run on a Vista machine. * The bootstrapper installs .NET 4.0 to allow my managed bootstrapper to work then prompts user to reboot. Machine is rebooted. * When I log in, the managed bootstrapper is launched and my install continues When the machine reboots, I have code within my DetectComplete to check "Bootstrapper.Command.Resume == ResumeType.Reboot". If true, continue with the install process automatically. This was done to handle a reboot scenario which can occur later. Following the scenario shown above, the user is never being prompted to accept a license or change settings in my UI because of this. How can you tell if the managed bootstrapper is being run for the first time? I'm missing a condition to make this work correct and I have no idea what it is. I'm sure someone out there has solved this issue and I would really appreciate the help. Thanks -Mike This electronic message from NAU Country Insurance Company and any attachment to it is intended exclusively for the individual or entity to which it is addressed. It may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized disclosure, copying, distribution or use of this electronic message or any attachment is prohibited. If you have received this message in error, please return it to the sender and delete this original from your system. 2828887 - 07 May 2013 21:01:05 - -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WebDeploy vs MSI
A question for the group, and Rob, I've been a big believer in MSI for 10 years now. If you were looking at deploying ASP.NET apps to an AWS environment, would you still package the app as an MSI or would you consider another paradigm such as WebDeploy? Thanks, Chris -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix & WCF
Hi Nick, Burn bootstrapper core is native Code, so it does not read .net configuration files. You can add a configuration file for your managed assembly which runs within the bootstrapper. You then habe to Olaf the configuration file by hand. Don't forget to add the config file to the payload. Regards, Markus Am 07.05.2013 um 20:48 schrieb Nick Miller : > Hi All, > > I have an interesting question for you guys. I am trying to get my custom > MBA to consume a WCF service that it installs after it completes. I've > successfully imported the service reference to the project, but when the > installer runs, it can't seem to find the endpoints in the app.config file. > My question is - is the app.config file ignored by burn? If so, it's not the > end of the world as I can add the endpoints programmatically, but I would > like to know either way. > > Thanks, > Nick > -- > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and > their applications. This 200-page book is written by three acclaimed > leaders in the field. The early access version is available now. > Download your free book today! http://p.sf.net/sfu/neotech_d2d_may > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
