Thanks. I can add this to the bug report for the tester to try.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-does-Windows-Installer-write-install-information-to-the-registry-tp7590115p7590125.html
Sent from the wix-users mailing list archi
A tester ran into an issue recently where the the machine got a BSOD near the
end of an install. While there is not a problem with the install itself,
the blue screen caused a strange side effect that I want to explain.
The install log indicates the install was successful and product is on disk
a
I am using the setting on the ExitDialog to allow the user to launch the
application when setup is complete. I want to hide this option if a reboot
is going to be required. Are there any properties that survive the
transition of the InstallSequence back to the UISequence that I can use to
determi
I would like to set a cue banner for an edit control in custom action in one
of my UI dialogs'. Calling IsAppThemed in my custom action returned false
which would indicate visual styles is not enabled.
I don't see any properties for the project that I can set to enable them.
Is it possible?
-
Finally got back into looking at this issue. The problem is related to using
the files from the the binaries download. After unzipping them to disk, the
files are locked since they were created on another machine. It would be
nice if the Windows Explorer visually indicated this similar to how is
I downloaded this weeks build, 3.6.2712 and I am getting this error building
my install project which currently builds with the 3.5 GA
Could not load file or assembly
'file:///C:\src\tools\shared\WiX\v3.6.2712\bin\candle.exe' or one of its
dependencies.
Operation is not supported. (Exception from
Entered bug 3431920. Attached a code example as well. Figure it is either a
bug or I am now getting caught doing something I should not have been.
Thanks and Good Luck Sounders.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CertificateRef-in-the
I am getting an install failure using a CertificateRef under a WebSite
element. This works fine under 3.5 but is failing under the 3.6 beta. If I
comment out the CertificateRef element, the install succeeds. The self
signed certificate which gets created earlier is getting added to the store.
I have seen a sporadic error in my installer where custom actions written in
C# exit but the install fails with the 1603 error when the action exits. I
put a log message just before the return and it gets logged but the install
fails. I checked and there are no objects that need to be disposed.
Check out the MsiLogging property. Windows Installer 4.0 and above is
necessary, but that will handle Vista and later.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Run-MSI-with-logging-from-Setup-exe-tp6311287p6312901.html
Sent from the wix-users
Thanks.
Bug 3066897 has been entered.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compile-error-using-ManagedPipelineMode-attribute-tp5527954p5534623.html
Sent from the wix-users mailing list archive at Nabble.com.
I downloaded build 3.5.2030 to test out the ManagedPipelineMode attribute
that was added to the iis AppPool element. The AppPool below
gives me the following error
error CNDL0038: The iis:WebAppPool/@User attribute's value, 'AdminUserReg',
cannot be specified without attribute Identity presen
Have you tried a recent build? Version 3.5.2020 added support for AppPool
managedPipelineMode and managedRuntimeVersion. I expect more things will be
added as 3.5 gets closer to releasing. For now, anything that isn't
supported I do through Custom Action calls to appcmd.
--
View this message
All setupbld can do is wrap your msi into the resulting setup.exe. It is
very basic in its functionality and if I am not mistaken, not really
supported anymore or at least no active development is taking place.
Yes, Burn is the feature you are going to want, as do many of us. It has
been delaye
There is defiantly a Domain attribute on the User element and if I don't set
that when adding the domain user to a local group, installation fails.
I had looked at USERDOMAIN initially but that gets set to the local machine
name when you are not logged in as the domain user. But, I suppose I cou
Are you getting the error early in the process, like around FileCosting?
Check a verbose log.
Ran into this a little bit ago and added the following property
Property Id="MSIRESTARTMANAGERCONTROL" Value="Disable" />
This resolved the issue for me.
--
View this message in context:
http://wind
Is there any way to determine if the user defined by the LogonUser property
is a domain user or a local user?
I want to add this user to a group but need to know if the user is a domain
user so that I can set the Domain attribute of the user element.
I there a registry entry that I can query on
Glad it worked for you. I am not so sure I am convinced that there is not a
bug as it should work with the different schedule types or a compiler should
be thrown for invalid ones.
If it is a bug, at least there are options.
--
View this message in context:
http://windows-installer-xml-wix-too
When are you scheduling the RemoveExistingProducts for the upgrade? I was
seeing this problem as well. I am using the MajorUpgrade element and had is
scheduled for afterInstallExecute. I moved it to afterInstallValidate
(which is the default) and my upgrade worked.
Not sure if it will work for
You can add the ServiceInstall element by itself without the ServiceControl.
Add the ServiceInstall in the same component that defines service file. The
service file needs to be the KeyPath. I would recommend not having any
other files in the components, which is good practice anyway. Somethin
Version 3.0 added an IIS extension.
http://wix.sourceforge.net/manual-wix3/iis_xsd_index.htm
http://wix.sourceforge.net/manual-wix3/iis_xsd_index.htm
Version 3.5 added support for II7 so I would recommend this version. As a
matter of fact you will likely want a recent build of 3.5 as bugs ha
One way is to create a CustomAction using the ExeCommand attribute. The
command line can be included as part of ExeCommand. Then add the custom
action to your InstallExecuteSequence. Since you want to run a file you are
installing, you will need to run the custom action after InstallFinalize a
OK. when I reread your post, it made me think that maybe the wxs file in
question is not known until build time. If that is not the case, then what
I told you should work fine. Otherwise, I would generate the candle and
light commands at build time adding the needing wxs file. But that is not
a
You add the wxs in to the call to candle which compiles the wixobj file.
Then include the wixobj in the call to light.
For Votive, you should be able to set this in the 'Additional parameters'
section of the 'Tool Settings' page of the WiX project.
--
View this message in context:
http://n2.na
I am trying to add and two WebSite and AppPools during installation and get
the errors listed below.
MSI (s) (68:A0) [23:32:30:219]: Executing op:
CustomActionSchedule(Action=WriteIIS7ConfigChanges,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (68:68) [
Does/will the UI for Burn allow me to let the user select products they wish
to install? For instance, if we distribute SQLExpress with our sysrem, can
I allow the user to select installing both or one of the components?
Also, is Burn mature enough to start using for a new new project?
thanks
You should be able to set up preconditions on those things in the msi.
Setupbld is not the place for that to the best of my knowledge.
JKLists wrote:
>
> My WiX project has a handful of prerequisites, for example, the
> application requires .NET 3.5 SP1. My WiX project correctly does not run
expect you'll find
> the
> issue quickly.
>
> On Mon, Nov 9, 2009 at 2:09 PM, John L Krupka
> wrote:
>
>>
>> Note: I forgot to mention that I removed the ScheduleReboot and I did not
>> get
>> the error message.
>>
>>
>>
>>
I know the policy msm is required as well. I don't remember what their
purpose is but they have some effect on the Side by Side system. Did you
look in the Event Log when installed with the policy files? I recall that
me a clue as to why they were needed, aside of course from the app not
runnin
I would add WiX to the list of considerations. I have used InstallShield and
Wise in the past. We decided several months ago to either migrate to WiX or
upgrade Wise. We chose WiX and have not looked back.
Unless you use the scripting engine of IS, which I would heavily advise
against, WiX wil
Note: I forgot to mention that I removed the ScheduleReboot and I did not get
the error message.
John L Krupka wrote:
>
> The setup executable that I am building with setupbld using the setup.exe
> stub crashes with a "The process terminated unexpectedly" message box.
>
The setup executable that I am building with setupbld using the setup.exe
stub crashes with a "The process terminated unexpectedly" message box. The
install requires a reboot, so the ScheduleReboot action is called. The
crash occurs after the reboot dialog is cleared. It does not matter how the
32 matches
Mail list logo