Still struggling with this problem. Here's an example of an XML file with the
structure I need to modify on install.
In my WiX code, I had:
which, of course, placed the text next to the Javascript processing
instruction, rather than within it. S
Pally Sandher wrote:
>
> That looks OK if it's passing the ICE tests now as it's much like the
> sample in the How to create a shortcut
> (http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm).
> Shortcuts are still files as far as the file system is concerned so
> copying that
In case you're reading HTML formatted, the greater- and less-than characters
got replaced by "& g t ;" and "& l t ;", without the spaces or quotes.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-you-change-the-text-of-an-installed-file-based-on
Those are both almost perfect, but I can't seem to figure out how to escape
certain characters in the value to be inserted. Specifically, I need to
insert some javascript:
but with that text as the value of the util:XmlFile/@Value attribute, it
won't compile (no surprise error CNDL0104). And ne
I've got an XML file that will be installed along with my app, which refers
to my app's installed executable. (Sort of like a shortcut, except that this
XML is used by a 3rd-party app to invoke my app as an add-on. My app can
also run as a standalone app.) I'd like to give the user who installs my
Oh, my bad. I forgot the
that belongs in each component. Still not an elegant solution, so comments
welcome. Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/installing-files-to-user-s-application-data-folder-tp5377311p5377751.html
Sent fr
I did find a work-around for the ICE64 errors, but it seems a bit clunky (see
below). Can anybody confirm whether this is the correct way to do this?
Chris Lord-2 wrote:
>
> With only one file in the component, you probably don't need the
> KeyPath. My WXS doesn't need the KeyPath for a file (I have a single
> file in each component) and it passes all ICE tests.
>
I would have thought so, but I get the same ICE38 error. Based on the MSDN
I'm a complete newbie to WiX and Windows Installer. I've worked through the
tutorials and documentation, and feel pretty comfortable with all the
basics. Now I'm trying to create an installer to fit my requirements, and
while the basic install of the app and shortcuts, including conditions, and
cu
I've read more about properties, so now I understand that there are private
and public properties, but I'm still confused on how to use them
successfully in my WXS file. (FYI, so far, I've just been playing around
with the examples from the http://www.tramontana.co.hu/wix/ WiX tutorial ,
so if yo
*Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: michaelr
Hi WiX users,
I'm brand new to WiX and was just a bit confused about the difference
between INSTALLDIR and INSTALLLOCATION. The WiX tutorial and samples seem to
use INSTALLDIR as the Id of the Directory tag, but when I create a new WiX
project in Visual Studio 2010, that value is automatically se
12 matches
Mail list logo
