I am trying to create a Compiler Extension. I started by studying the
WixContrib project along with various extensions in the Wix source, like the
Gaming extension. I had previously created my CA and wixlib projects using
a custom defined table in the wsx, and now I have the WixExtension working,
Ignoring ICE38 worked. I also ignored ICE91 as well but that was just a
warning anyways.
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 7:33 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progi
I also love the idea of per-user installations, but they aren't the best
supported thing from an authoring perspective that's for-sure. From having used
MSI at varying levels for a number of years, the only two rules I have come up
with is anything that is easy isn't and that I/we/they probably
It is a 100% pure per user install. :) I'm installing to AppData/Local.
Just testing the waters with per user installs since I only did per machine
before. Surprisingly not much guidance out there which surprises me since I
thought Microsoft encourages per user. I know they did put in bette
Are they MSI packages? If so set visible to true. The bundle will still
appear in ARP. EXEpackages you can't do this.
-Original Message-
From: GrahamAllwood [mailto:graham.allw...@live.co.uk]
Sent: February-11-14 6:45 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bundle
The issue involved in that requires you log in via another user, which is
impossible for a per-user installation. If you are installing per-machine then
ICE38 does, in fact, apply to you, you cannot use an advertised shortcut here,
and probably should seriously reconsider installing an executabl
Hi
I have a Bundle that contains 4 Sql Server Components (SMO, RMO etc) and
finally my own APP msi file.
Is it possible to have all the 5 separate installs to appear in Add/Remove
programs, or does my Bundle have to act as the parent to all of them, and it
is only the Bundle that can appear in AR
According to here a HKCU keypath is important for self-healing:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/A-method-for-avoiding-ICE38-error-td712044.html.
So looks like not a good idea to ignore it.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.c
ICE38 is an error when I build in wix. Can you ignore ICE38 errors?
Error 1 ICE38: Component CMP_Rapid installs to user profile. It must
use a registry key under HKCU as its KeyPath, not a file. C:\Users\Wesley
Manning\Desktop\APP-0014, RapidCore Configurator\Installers\ShellSetup\Co
Since that is the case, ICE38 is (in my opinion) incorrect and you will want to
ignore it. ICE38 implies you are installing per-user resources in the context
of a per-machine installation but never verifies that this is so.
Actually authoring a per-user install requires that you ignore ICE38 be
I finally figured it out.
The of the build file needs to be set to 'Bundle' and I also
need to include the WixBalExtension using the element.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSBUILD-and-Burn-tp7592535p7592592.html
Sent from the
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using adv
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Miss
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Origi
To answer my own question, don't use an outdated MSI with a newer CAB file
(though I am still not certain why it caused the issue). I was under the
impression that if the CAB was signed there was no additional verification done
on the CAB. If in fact it was using two different certificates t
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet I
AFAIK, there is one feature request for an additional XxxRef: ConditionRef.
Everything else has seemed reasonably doable with existing reference elements.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant
Looking at the issue from a different perspective, if you refference anything
that is in a fragment, then everything in the fragment is added to the
package. Many elements, like Component (for example) have a corresponding
XxxxRef element, which you use to reference the element in another fragment
I don't know why it wouldn't be possible. Advertised shortcuts are one
of the entry points for repair, and I'm pretty sure repair works fine
on per user installs.
The process is a potential repair - the shortcut checks that the
component target is there, and if not installs it and repairs the
pare
I'm having a strange issue with an installer (using WiX and Burn). We've put
out about 15 updates (all major upgrades) without any problems. Now the
latest update is causing the icon on the desktop shortcut to disappear on XP
(leaving us with the default windows shortcut icon). The icon is fine
I'm not sure what most people do, but here is what I do:
For my wxs file testing, I just use LINQ to XML and verify properties of
certain things that I do not want to change (i.e. perMachine installs,
etc.) I do the same for other types of things, like SQLScript (verify that
the sequence is sequen
What does the log say about the WIX_ACCOUNT_LOCALSYSTEM value? And in
the services control panel stuff, what is the Log On value in the
properties?
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1
Great ,working! thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Caching-external-language-file-with-burn-variable-tp7592498p7592576.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Hello, I am using WiX along with VS2012.
Let's say the files are like this:
Product.wxs:
...
UI.wxs:
InstallUISequence.wxs:
...
InstallExecuteSequence.wxs
...
I separated the last two parts of code into two files. It appears that they are
not reflected in MSI package when I v
This isn't completely accurate:
" am doing this but I feel this is not the way to make the build
automated because instead of changing the Product version in
Product.wxs we have to change the assembly version of actual exe OR if
we make the assembly version of actual exe to increment automatically
We are moving to Visual Studio 2013 and my current project i built in
Vs2010 is a wcf service hosted by a windows service. I created a setup
project and all worked as expected.
Moving to 2013, setup projects are no longer supported. I tried the
InstallShield lt, its a sham trying to get us to spen
It's not hard but there is nothing built into WiX toolset today to do it. There
is a feature under development to do self-update for bundles that could help a
lot building an auto-update system.
You just have to connect a few more dots today.
My approach was to make the burn bundle responsible for the updates just like
it was responsible for the initial install. With that, I have submitted some
core changes to WiX which are currently in limbo of being accepted as the
Detect call now requires a HWND to be passed. If and when the self
Thanks for your reply. I tried looking at http://powerprogrammer.co.uk. but the
website doesn't seem to be current.
I tried posting comments/download trials but it's unresponsive.
I like the concept of simply referencing a dll in the application to handle
auto update.
I have done some research a
Hello,
I am new to the world of WiX, and installer in general. The major
question that I have at this time is how to unit test both the WiX and
the MSI that I create. Should I just setup a VM and try the installs
there or what? How do you guys test these projects?
Thanks for your attention.
I saw that SharpDevelop (open source version of visual studio) works with Wix.
MSBuild may be good to know though.
-Original Message-
From: GrahamAllwood [mailto:graham.allw...@live.co.uk]
Sent: February-11-14 12:39 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bundle
Thanks for the reply.
I did follow the docs yes, but I must have missed the two lines on the end,
the ones that tell you how to compile it. I see from this I think I have
missed out including the WixBalExtension.
I only have VS Express so can't run Wix inside VS :(
Thanks again.
--
View this
I have been having problems creating an installer that will install and
start a Windows Service.
This is on a Windows 8 64 bit PC VS 2012 WiX 3.8
I have created a very simple windows service that writes to a text file
when it is running as a test.
This is almost a direct copy from the WiX 3.6 De
Did you follow instructions here:
http://wixtoolset.org/documentation/manual/v3/bundle/ ?
You should have all MSIs in the element in the bundle. Your right,
there is no product element in burn.
Did you try building it via visual studio first?
-Original Message-
From: GrahamAllwood
Hello.
I'm tring to create a bundle and I have created my wxs file containing my
element.
I'm not sure what to do now! I want to use MSBUILD, but when I do, my wxs
file compiles ok but LIGHT fails because it can't find a element.
There is no element in my files as this is just a bundle.
Shoul
Thanks Walter, that would be really helpful if you can give me an example.
Regards,
Suvra Jyoti
On 11-02-2014 19:53, Walter Dexter wrote:
> It may not be the most elegant way, but I'm doing the same thing by passing
> the contents of the file (first line anyway) as a command line argument to
> th
I change the logging level of our services based on a MSI property
I have it set up like this:
MSI: (product.wxs)
I can overwrite that by running MSIEXEC.exe /I
SERVICESLOGLEVEL=DEBUG
BURN: (bundle.wxs)
I also have a burn project and in my bundle.wxs I have:
Then in my MsiPackage element
Take a look at this thread:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-td7589150.html#a7589177
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Set-Product-version-in-Product-wxs-file-tp7592487
Modify the wixproj. You can do the heavy lifting in MSBuild and then just pass
the constants across.
Ex:
$(DefineConstants); SVNInfo=$(SVNInfo);
As for the string tokenizing, you could write a simple inline task to strip
everything after (and including)
Take a look at this thread:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-td7589150.html#a7589177
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Read-a-value-from-a-text-file-and-use-it-in-WIX-s
Win 7 x64, CAB is 50 MB.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, February 11, 2014 9:21 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Digitally signed MSI with signed external CAB's
On 11-Feb-14 10:11, Hoover, Jacob wrote:
>I'
On 11-Feb-14 05:22, Holpp, Stefan wrote:
> MSBUILD : PKG error : ID E6125: *** : File version for Assembly
> 'C:\dir1\dir2\someExample.dll' (feature 'EXAMPLE') not found. ...
> [C:\WS\TEST.wixproj]
That's not a WiX error message.
--
sig://boB
http://joyofsetup.com/
---
On 11-Feb-14 10:11, Hoover, Jacob wrote:
>I've been signing and deploying for several years now, but with the latest
> release I've ran into a strange problem. The first error complains about a
> difference in size between the certificate in the CAB verses what's in the
> package. The secon
Bob do you want me to file a bug, or has this been done already?
On Thu, Feb 6, 2014 at 6:35 PM, Bob Arnson wrote:
> On 04-Feb-14 07:40, Tony wrote:
> > votive install contains wixcomplusextension.dll and wixmsmqextension.dll
> > wix38-binaries contains retina.exe (and config)
> That would be a
On 2/10/2014 8:22 PM, Chetan Rajakumar wrote:
> Hi Dave,
>
> Can you please let me know what all changes you are making for this.
> Please let me know what code you are writing in python script, Is this Script
> placed in Wix Installer project?
> How you are setting command line parameters which u
Will try this and let you know, thank you!
On Tue, Feb 11, 2014 at 8:27 PM, Tunney, Stephen
wrote:
> And please excuse the poor formatting of my message :)
>
>
> -Original Message-
> From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
> Sent: February-11-14 9:56 AM
> To: General dis
I've been signing and deploying for several years now, but with the latest
release I've ran into a strange problem. The first error complains about a
difference in size between the certificate in the CAB verses what's in the
package. The second error is a bit comical complaining that the digi
It looks like @AnonymousAccess is not a formatted type so it does not accept
the property.
You would need to author two mutually exclusive components that differ only by
AnonymousAccess and use the passed in condition as a component condition.
Dave
-Original Message-
From: Kiran Somise
Can you use advertised shortcuts in a per user install that installs to a per
user location (e.g. LocalAppDataFolder). From my searching it doesn't appear
possible.
I asked this over a week ago but got no responses. I'll try one more time. :)
-Original Message-
From: Wesley Manning
Where should we declare "PASSED_IN_VALUE" in the wxs file?
Can you pls throw me a sample wix file to handle this.
On Tue, Feb 11, 2014 at 7:54 PM, Levi Wilson wrote:
> You can use something like this:
>
>
> And then when you run your installer:
>
> msiexec /i YourMsi.msi /l*vx output.log PASSE
You can use something like this:
And then when you run your installer:
msiexec /i YourMsi.msi /l*vx output.log PASSED_IN_VALUE='value passed'
the /l*vx will log the install to a file. From there you can see what value
PASSED_IN_VALUE gets. I didn't run this, but it should be pretty close to
wha
This looks like an issue (perhaps not a bug) with WIX schema validation during
compliation of the wxs file. It is checking your .wxs file against an xsd
schema that limits the possible attribute values for @AnonymousAccess to the
literals "yes" and "no".
I've hit this before with other items a
And please excuse the poor formatting of my message :)
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: February-11-14 9:56 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] how to pass values from command line to wix installer
Th
I have declared the property like below
yes
using it like below
but when I compile the project I am getting below error
Error 3 The iis:WebDirProperties/@AnonymousAccess attribute's value,
'[VALUEPASSED]', is not a legal yes/no value. The only legal values are
'no' and 'yes'. C:\Infodev\TRFA
If you need to pass information into an MSI at runtime you need to author a
public property.
http://msdn.microsoft.com/en-us/library/aa370912(v=vs.85).aspx
You should also remember what was passed in from the command line or it will
revert to default on a repair or patch, see:-
http://robmensc
You have to use ExePackage and set Protocol="burn". Then the bundles will be
inlined and you'll only see one gui.
Wes
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: February-11-14 2:47 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-use
You should use Property for example:
Then run msiexec /i abc.msi VALUEPASSED=yourvalue
On 2/11/14, Walter Dexter wrote:
> If you mean when you install the resulting MSI, that would be in the
> Windows installer documentation. Or you can do msiexec /? and I think
> that's in there.
> On Feb 11,
OK. I'm convinced this is the way to go. Burn it is.
Graham
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstapper-and-Software-prerequisites-tp7592516p7592533.html
Sent from the wix-users mailing list archive at Nabble.com.
It may not be the most elegant way, but I'm doing the same thing by passing
the contents of the file (first line anyway) as a command line argument to
the linker.
I use a .cmd file to run the WiX ci mpile and link so its just a bit of
batch file processing.
If you need an example I can get it for
I got this link.
I am creating the msi using the msbuild.
variable delcared:
msi name: trfaudit.msi
command line : msiexec /i trfaudit.msi -dacces="no
This didn't work.
On Tue, Feb 11, 2014 at 7:21 PM, Giona Imperatori <
giona.imperat...@gmail.com> wrote:
> Are you sure? Try to look better
If you mean when you install the resulting MSI, that would be in the
Windows installer documentation. Or you can do msiexec /? and I think
that's in there.
On Feb 11, 2014 7:42 AM, "Kiran Somisetty" wrote:
> I have a requirement to pass values from the command line while
> installing the wix.
>
Are you sure? Try to look better the next time:
http://wixtoolset.org/documentation/manual/v3/overview/preprocessor.html
2014-02-11 14:30 GMT+01:00 Kiran Somisetty :
> I have a requirement to pass values from the command line while
> installing the wix.
>
> I want to assign this to Anynymo
I have a requirement to pass values from the command line while
installing the wix.
I want to assign this to AnynymousAccess attribute.
Can you pls help me on this, I searched the documentation, but haven't got
any clues.
Kiran
To the first doubt:
Forget the MedAssemblyLocation="Default" attribute, I was testing with it, but
the actual issue is completely independent of it. Removing it does not make any
difference ;)
To the second doubt:
None of the affected assemblies are in the GAC.
-Original Message-
From:
What is: MedAssemblyLocation="Default"? I don't recognize that attribute.
My first guess is that this file is being GAC'd but the other file wasn't.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
Hi all,
I am using Wix to create a msi package which shall do nothing special than just
installing a bunch of files to specified locations.
The corresponding snipped of the .wxs file looks like:
[...]
[...]
67 matches
Mail list logo
