Thank for your replay ,
At present situation its difficult to migrate to Wix 3.x,
In this scenario updating "WixUI_en-us.wxl" is the standard practice ?
Thanks
Naufal
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, September 28, 2010 10:03 PM
To: wix-u
Ok, so the size of the installer was sorted quite nicely. Thanks to
all who helped.
Now on to two more issues I can't seem to get around.
1) I am trying to include Crystal Reports in my installer, as my
software depends on it.
Using this .wxs:
http://schemas.microsoft.com/wix/2006/wi";>
Go figure...in the example (http://www.tramontana.co.hu/wix/index.php)
I was following, they even mentioned making an .ico or .exe to hold the
icon if the file size was to big. I read the example yesterday, and did
not see that again until you said "provide an .ico file". *sigh*
Thanks for th
Sounds like you are doing this in a merge module. Just add
It'll teach the compiler to not do that but also not create a row in the
property table since you didn't give it any value.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really go
Okay, thanks, it seems like the built-in MSI variables might be the
way to go rather than grabbing it from the environment variables.
When I try using the MSI variables, however, the value that ends up in
the MSI is:
[CommonFiles64Folder.2312FADD_90E2_487F_B4BC_5B3F1489FB3C]\path\to\folder;[Commo
I think the Icon SourceFile is stored in the MSI package in the binary table
(Is this correct?).
What's the size of MyProg.exe? 48.5MB? I think you can dramatically reduce the
size of the MSI if you can provide a .ico file as the Icon SourceFile rather
than the .exe itself.
Of course, this i
Here is my exact .wxs file, with GUID's changed of course. I also made
sure to remove other sensitive information as needed.
http://schemas.microsoft.com/wix/2006/wi";>
<-- See below for why this is commented out. -->
There is a provision in Windows Installer for supporting/generating a
multiple disk installation, so that a large install could be shipped
on floppy disks.
A bit of digging into the WiX / MSI archives will provide the info
that you need - be glad you're shipping in 10MB chunks and not 1.44MB
chunk
I think an example of your authoring might help here. I have a number of small
packages with embedded cabs and they are each between 2MB and 4MB. Small
packages are certainly possible...
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-6
I just started using WiX today, and so far I am liking it's potential.
But, like all new things, I have some questions about WiX.
The major questions I have relate to how the installer is packaged. Due
to some restrictions on the FTP server I must use, I need to split the
installer file up in
IIRC:
That should work no matter which currently released framework(s) you have
installed (excluding 1.x, of course).
-Blair
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, September 28, 2010 3:55 PM
To:
The other sections of log from earlier in the mail thread are not from the same
log as this newer section of log. Different portions of the same log sometimes
have to be taken together, and representing spew taken from different logs as
being from the same transaction doesn't make it easy to pro
That's much better, but I still needed the code that reads the InstallLocation
into my property.
Thanks!
> -Original Message-
> From: jhennessey [mailto:jack.hennes...@hyland.com]
> Sent: Wednesday, September 29, 2010 10:10 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-us
You should schedule it before LaunchConditions in both the InstallUISequence
(I'm assuming you are using standard MSI UI) and InstallExecuteSequence.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/sequencing-custom-actions-tp5573077p5584163.html
Se
Burn does not require the .NET Framework, you can code your UX in native code
if you want to. (The WiX 3.6 installer is using managed code for the UI so
it installs .NET for you before presenting the UX.)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.
If you set the ARPINSTALLLOCATION property to the value of INSTALLLOCATION it
should work:
NOT
Installed
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Directory-in-Maintenance-mode-is-not-directory-installed-to-tp5580924p5584068.html
Sent f
I solved it!
I don't know if this is the most efficient or preferred way, but here's what I
did:
I created a component that is in the main feature that is always installed. It
creates a registry key that contains the INSTALLLOCATION value. Such as:
Then, I created a property that reads
That didn't work. I'll keep plugging away, but if anyone can see a possible
cause of the problem, please let me know.
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Wednesday, September 29, 2010 6:08 AM
> To: General discussion for Windows Installer XM
What rub's me is how the Windows Installer Team talks a good talk about Agility
Trends in Packaging and "No Support for Managed Code" while DevDiv goes off
and makes the investment that raises the bar. The rest of the world is faced
with either investing huge money to get this functionality as
On Wed, 29 Sep 2010 11:14:35 +0100
"Pally Sandher" wrote:
> You'll need to write your own bootstrapper or ExternalUI rather than
> use the built in Windows Installer UI.
>
> Burn will eventually offer something similar to that experience from
> what I've heard/read but until it's done (which cou
You'll need to write your own bootstrapper or ExternalUI rather than use the
built in Windows Installer UI.
Burn will eventually offer something similar to that experience from what I've
heard/read but until it's done (which could be a while yet) your only option is
to roll your own. dotnetinst
Try removing the ConfigurableDirectory attribute from all but your top
level feature. I think that could be confusing Windows Installer about
where to put the sub-features. Could be wrong though but it's worth a
try.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
Thanks for the reply. I tried setting width to a localization string but i
got the error:"error CNDL0008: The Dialog/@Width attribute's value,
'!(loc.canceldlg_width)', is not a legal integer value. Legal integer
values are from -2,147,483,648 to 2,147,483,647."
Am I missing something?
--
View t
23 matches
Mail list logo
