Thanks Phil.
We at first did use Profile="all", but it was decided that we did not want
our program to have Public firewall access. So we figured that we would
simply create the 2 entries, one for Domain and one for Private. But as
stated above only Private gets enabled and Domain does not.
So is
Sorry for taking you away from Torch work Phill.
Now with my code my Id's are different, so it is not that that is causing
the issue, but I noticed that you are not using the File or Program elements
and you also have your Scope set to 'localSubnet' where as mine is set to
'any'.
If you do n
Okay I changed the Name entries and it finally worked
So this works, but it would have been nice to be able to use the same Name
as we let the app run without the firewall entries and it prompts for
firewall exception then it will create the entry using the app name and
therefore there is only
Okay newbie question here concerning the updating of a .config file during
install, using WiX 3.7.
I was given the task to update a new .config file during our install and I
found the documentation for XmlConfig Element (Util Extension):
http://wixtoolset.org/documentation/manual/v3/xsd/util/xmlco
Okay I tried the following:
This one did nothing at all, no errors, but did not update file. So I tried
the following:
And this one did create the entry, but not how I was expecting it to be
created. Above is what I wanted/needed, but what was created with this line
is as follows:
...
Okay I am re-looking at the XmlConfig method as described in the following
link:
http://sourceforge.net/p/wix/mailman/message/20326106/
And when I use the example that is in that link I get the following failure
in the install:
Failed to find node:
//configuration/appSettings/add[@key='ServiceInf
I have just been given a task to update one of our apps .config file and so I
tried what was listed in this topic but I am getting the following error:
Failed to find node:
//configuration/appSettings/add[@key='ServiceInfo'] in XML file: C:\Program
Files (x86)\CompanyName\Product\Product.exe.confi
Thanks eyoung, I made the recommended changes:
But when I build the install I get the following error:
C:\Work\Projects\Lync2013SP\RemoteInk.Lync2013SP\Src\Client\Installs\Client\Product.wxs(85,0):
error LGHT0204: ICE03: Invalid format string; Table: XmlFile, Column:
ElementPath, Key(s): SetSer
Thanks John, I made that change and the build worked but when I ran the
install to test it I get the following error:
Failed to find node:
//configuration/appSettings/add[@key='ServiceInfo']/@value in XML file:
C:\Program Files (x86)\CompanyName\Product\Product.exe.config, system error:
-214702058
I added the Name="value" entry, but I still get the same error???
So I am still at a loss as to what I am missing or doing wrong to get this
to work
So in the error message when it states: 'Failed to find node:
//configuration/appSettings/add[@key='ServiceInfo'] in XML file"
What is it sta
Okay I must be missing something as as I mentioned above this one did write
to the file, just did not write it correctly:
When I update this to:
Basically the same thing except for the add[\[]@key='ServiceInfo'[\]]" and
then run it I get the 'Failed to find Node:' error. So why would adding t
Well I created the Sample and it worked correctly, using exactly what was
shown.
So then I simply substituted my app.config file with the sample.config file
and built and ran the test again and it failed?
So I figured that it was my .config file that was the issue, but then I
simply added the fo
Okay do you have a small example of using XmlConfig to create and set the
value of a key, as I was also trying XmlConfig and I did not get any errors,
but it did not do anything to the .config file?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nab
Okay still having an issue with util:XmlConfig. If I use the following:
Then the install will work and no errors, the .config file will look like
the following:
As you can see the ClientMode is in the wrong location, it should look like
this:
Bob, what was the 'normal' custom action that you used at the end of the
install to launch your app with arguments?
I was also using LaunchApplication to trigger the launch of my application
at the end of the UI by check box selection, but I also needed to supply
arguments and therefore it did not
This does not work if the file you want launched is installed through a merge
module or wixlib as you can not specify the FileKey to an Id that does not
exist in your main wxs project. So what other methods are there to launch an
installed app at the end of the install that requires arguments that
Okay I do have this working now, but have one more question on this...
If the element keys exists and you only have to change the values then we
can simply use the XmlFile action="setvalue" method.
If the element keys do not exist then I had to use the XmlFile
action="createElement" and a few "se
I have looks at the WiX 3 Tutorial: Custom EULA License and MSI localization:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-EULA-License-and-MSI-localization.aspx
And see how they had to actually modify the LicenseAgreementDialog.wxs file
to accomplish this, but as st
Thanks Rob.
No I have not seen this. I am definitely not a high end developer as I do
mostly install related development, but with that said I could always have a
sand boxed look at the code and see if I can figure out how to implement and
test.
What would I need to be able to look at/modify/buil
Okay, since for now I have to use the modify method for the License dialog
found another issue that would be nice if it could be supported as well.
In the tutorial the set the following in the language string files:
\Lang\en-us\EULA_en-us.rtf
But my path to the EULA's was declared in a vari
Is it possible to reference a wixlib within a wixlib project?
I am re-asking this as I had no responses to the inquiry I posted back in
January:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problems-with-referencing-wixlibs-within-a-wixlib-project-td7591687.html
It has been a whi
Piping in a little later here, as had no requirements for PowerShell custom
actions but now do.
Our product team is developing a Server app and require a bunch of
PowerShell actions to be ran, some only require triggering commands that are
used to log server info, but others are more detailed/comp
Thanks for the information John.
I'll prompt the developers on if they know what modes the servers will be
ran under, but I would figure that it would be "Restricted".
I do not have much/any experience in creating C#, so are you suggesting a
wrapper .exe or custom action dll, which would therefor
I am trying to do a MaskedEdit control that can contain 0-9, so I set the
text to # and I have a default of 2279.
When test the dialog box the Next button will do nothing until I enter 5
numbers in the MaskedEdit control.
So what am I supposed to set the text field to so that I can enter
Thanks John, but yes I have seen that article and it still does not explain
how you can enter 1 to 5 numbers in the field.
If I change enter 1, 11, 111, the next but will fail to do anything,
but if I enter 1 then the install will proceed as expected.
So it seems that if the text field h
Thanks John.
After a bit of frustration I finally figured out my issue, it was one of my
conditions on the publish events that was screwing me up. Now that I fixed
that I can correctly enter 1 to 5 numbers and have it do what I expected it
to do
--
View this message in context:
http://wind
I was actually using a PORT_NUMBER > 0 conditions before I switched to
MaskedEdit and therefore once I switched I did not remove that condition as
the mask # does not accept negative numbers and therefore I did not need
that condition. Once I removed it then it began to work as expected.
--
I have seen many WiX articles on detecting .NET 4.5 or greater and I have
implemented the recommended entires, but my install will FAIL to detect .NET
4.5 on machines that have .NET 4.5 and 4.5.1.
Now we are still using WiX 3.7, and therefore if the machine has .NET 4.5.1
does the NETFRAMEWORK45 n
My condition is:
Again we are still at WiX 3.7 so will not be able to look at the 3.8
functionality until we move to that version in our build environment.
I have not yet looks into the registry keys, but I guess that I should if we
support 4.5, but most of the machines that we will be installin
Okay now I am experiencing another issue with this.
Since I have set my Text to # so that I can accept values from 1 to
9 it is actually back filling my property with spaces if I enter less
than 5 numbers.
So if I enter '34' the property would end up being '34 ', meaning the
string now
That's the think though, I checked the install log after it failed to find
.NET 4.5 and the NETFRAMEWORK45 property was not generated at all. So if in
WiX 3.7 it will detect 4.5 and greater then it should have at least created
that property with the version that it found.
So why did it not do that
Yes, I should have netfx linked in. It shows in my project References and it
is listed at the top of my wix project:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";>
Now we build through msbuild - building the main solution file s
Well I feel like an Idiot I was declaring and missed the Ref part of it and did not even noticed after all the
examples that I looked at
Sorry for all the hassles that I put you through. I'll give it another shot
and more than likely it will work now..
--
View this message in con
Okay changing the property to PropertyRef fixed the issue.
The MsiNetAsseblySupport = 4.0.30319.33440
The NETFRAMEWORK45 = #378675
Which means that what is installed is: 4.5.51641
So I am good to go. Thanks for all the help.
--
View this message in context:
http://windows-installer-xml-wix-
This could be a simple question, but at the moment I just can not see it...
For push buttons and check boxes we just add the & in front of the
character that we want set for controls Alt hotkey, but if you have Edit and
MaskedEdit controls how do you set it's controls Alt hotkey?
Thanks.
--
Vi
It was a request from one of our managers as they noticed that they can use
Alt-Hotkey on the Change Directory dialog box, even though this is a
built-in MS dialog box. But that dialog box can do it so they wanted in in
the main installer as I have a Custom Dialog box that has 5 edit controls
and t
No I have not tried that so I'll give it a try.
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-Dialog-box-edit-controls-and-setting-Alt-hotkeys-tp7595958p7595962.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Okay thanks Rob that did the trick. I had to make sure the static text
controls had Tabskip set to 'no' though to get it working. But all good
now
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-Dialog-box-edit-controls-and-setting-Alt-h
We are randomly get having out WiX builds fail with the following:
[Light] light.exe error LGHT0001: Cannot create a file when that file
already exists.
The log does not indicate what file it is complaining about and I have not
seen any other reports of this error in the groups.
Has anyone seen t
Thanks Phill,
I do not think someone would have been on the TeamCity build machine opening up
files at the times of the failures, so that should rule out that case. We have
a build step that will generate a new Product Code for the product and replace
the one in the WiX projects, but that again
Yes this all works and all, but is there no way that we can have say some
text with a description of what will be launched?
I have a WiX .msi installer that contains all the standard and custom UI
that we need and it contains the check box at the end of the install for the
user to launch our admin
There are a bunch of Burn built-in variables that we can use, but if what I
want is not included in that list then how can I go about declaring a new
variable that gets a standard environment variable?
Basically what I need is to get the %USERDNSDOMAIN and %USERDOMAIN
environment variables and app
Thanks Rob...
Since I have not yet had to do any Burn customization is there any samples
that would help me get started on how to customizing the
BootstrapperApplication?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-built-in-varia
Okay I was able to generate a check box field at the end of the bootstrapper,
but now I need to know how it actually gets triggered to launch the app?
Here is what I have in the theme file:
#(loc.SuccessHeader)
#(loc.LaunchAppCheckbox)
#(loc.OptionsOkButton)
#
I am updating the WiX 3.8 to see the differences in the updated Bootstrapper
and therefore I am looking at the following page:
https://classicwixburntheme.codeplex.com/wikipage?title=Guide%201&referringTitle=Documentation
Just to follow the example it states to download 1033.zip and extract the
Cl
Sorry, Rob but I am still at a loss here as how what I would need to update
to be able to get the values of these environment variables into the WiX
burn bootstrapper that then get passed to my .msi installer. Again I am not
up to date with programming skills and therefore having to update code is
Okay so it is not as easy as adding a new control to the Success Page in the
theme because as stated I did that and it shows no problem, but have
basically no control over this and it's execution. So the actions that were
on the Launch button has to be switched actions that get triggered only if
th
Thanks Rob, I'll do that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Where-to-get-the-ClassicTheme-xml-wxl-Bootstrapper-files-tp7596697p7596704.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Yes I already do this, but I was trying to get the value so that it could be
appended to a property that gets passed to the main installer. Since what gets
passed to the install will override what defaults gets set in main install
those and therefore you lose the entries. I'll figure something o
Oh and one more thing about customizing the burn bootstrapper theme files. I
figured that if it was too much work to simply add a checkbox on the success
screen and have it set to launch the app on finish, I figured that maybe
just add a text control at the bottom that then informs the user what th
Okay I have another question about the masked edit field. If we have a PID
that contains only letters and numbers then is there a maskededit setting
that will ONLY allow this mix of characters or is this something that it can
not handle and therefore other actions would have to be used to validate
Joe, did you ever get the MaskedEdit control to only accept Upper/Lower case
letters and numbers?
I am trying the same thing and I just want the MaskedEdit to only access the
same thing, but at the moment it will accept all characters and then I have
to create conditions/CA to validate to make sur
Tim Mayert
Subject: Re: PIDTemplate w/ MaskedEdit
According to this:
http://msdn.microsoft.com/en-us/library/aa733654(v=vs.60).aspx
all uppercase A might be what you need.
---
Phil Wilson
On Tue, Sep 9, 2014 at 2:30 PM, TimM <[hidden
email]> wrote:
> Okay I have another questi
I have a MaskedEdit control that can either be blank or filled in. If blank
then next button will continue, but if any characters are entered then I
only want it to continue if all the required characters are filled in. So is
there some built in method to validate that all characters have been fill
Coming back to this one just to see if there may be another reason for this
issue. Again it does not prevent out apps from running at the end of the
install, it is just an issue of seeing sxs errors in the Event Viewer.
I checked the app .exe manifest files and yes all the assemblies that are
decl
No we are not doing nested installs. Since Wix does not support an admin
chain install that creates a output .msi we are using InstallShield to
create our chain installs to chain all out wix install projects.
We have quite a few wixlib 32 bit assemblies that we create to that gets
installed and ar
Yes that is basically what InstallShield is doing and again the only reason
that we are still supporting this is that we still have administrators that
push out our software by .msi only and therefore we had to support a multi
.msi package so that they only had to push out a single .msi file instea
We have some advertises and some that are not. I'll have to check if the apps
to the shortcuts that are advertised are the only ones that produce sxs in
the event viewer during installs. If so then I'll check to see what happens
if I turn advertisement off.
Thanks.
--
View this message in conte
Does anyone know of a way we can detect if there are pending Windows Updates
or currently running Windows Updates?We have seen this issue quite a lot
where we have 32 bit assemblies within our installs that get installed and
then published near the end of the install. But if there are pending Windo
Our testing department has been doing some install/uninstall testing with our
products and have reported that sometimes the uninstall can be very slow at
times and therefore wanted to know if we can fix these.I reviewed the logs
and there were no indication of any tasks taking an overall long time
Nope the VM's are strictly captured snapshots and therefore no accumulative
changes are applied to the images.
Another thing to note is that we have our own uninstaller application that
simply launch the uninstalls of our products that are selected by the user
and the tester noticed that the slow
Here is the download link to the uninstall logs:
https://www.dropbox.com/s/5qivuotwbornc8t/UninstallLogs.zip?dl=0
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-running-very-Slow-tp7600812p7600828.html
Sent from the wix-users mailing li
I would like to know if there is a way to detect what triggered a product
uninstall.
Issue: We have some custom actions that should NOT be triggered if the
install is running in Upgrade mode. This is true for the upgrade install,
but the custom actions in the previous version, that is being uninst
Okay I have been searching around and found the following property:
UPGRADINGPRODUCTCODE
I totally forgot about this property and therefore this is the one that I
should be setting my custom action conditions on.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559
101 - 164 of 164 matches
Mail list logo
