Hey WIX Users,
I am using WIXv3 3.0.2921 build. And I am able to use automatic
component guid generation as stated by Derek in:
http://installing.blogspot.com/2006/09/automatically-generating-component.html
I also understand that this is a new feature in
Hi,
I'm new to WiX and have been trying the WiXEdit tool to build an installer.
I have been working through a turorial and successfully built the initial
MSI file with a custome dialog to collect user information that will be
written to the registry but now I have come up against a few issues I
Have you checked out https://sourceforge.net/tracker/?
func=detailatid=642714aid=1656236group_id=105970 yet?
One trick is to set a property with the folder first and than add a
filesearch using that property.
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oct
To set a default property value use the Value attribute in the
Property tag. If the search does not find a value that value should
be used.
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oct 12, 2007, at 9:18 AM, RussGreen wrote:
Hi,
I'm new to WiX and
The value from the UI is stored in a Property which you can then use
in the IniFile under a Component.
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oct 11, 2007, at 6:09 PM, 0x001A4 wrote:
I have a dialog in which users are going to be entering
Here is what you need to do to make your install package smart to
recognize removing itself if it is already installed.
1. Product tag line, the Id= GUID needs to be Unique each time you
build the package (and the version number needs to be incremented each
time as well)
2. In the
My name is Guna S. Am very new to Wix Installer
This is regariding to Silent Installation
My questions are
1. How to create and add DLL file
2. For silet instllation if user gives command(for ex xxx.msi/quite), so
for this how the confiuration file should be
3. How/where to put condition for
At which point in the install should I add this though? Should I add this
somewhere in my main wxs file with all of my other components? If I were to
go about it that way, would I then be able to put the info in an ini file
after all of my installation files are copied over?
Sorry for the newbie
The FileShare element should do that.
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oct 11, 2007, at 11:58 AM, Craig0ss wrote:
Hi
I need to know if its possible to share a directory as part of the
install??
If this is possible any ideas on how to go
On your Package element I'd change your Id= GUID to be the question
marks so it auto generates each time. Or just change the GUID manually.
Package Id=----
autogenuuid (Simple Type)
Description
Values of this type will look like:
Thanks Chad,
I tried that. I built the installer and installed it on a test machine. I
then changed the product version from 2.3.2836.20968 to 2.3.2836.20970 and
generated a new product GUIDeverything else stayed the same. I then
rebuilt the MSI and ran it again on my test machine and got
I use the same control in my installer to allow the user to choose the
destination folder. I purposely set Remote=no and Removable=no so
they can't install to those locations. But, just out of curiosity, I set
them both back to yes and rebuilt my installer. When I get to the
dialog with that
hi there
i am currently having the same, and have not yet found a salution, however
if you want your floppy to be seen in the combo try this
Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55 Width=220
Height=80 Property=_BrowseProperty Removable=yes Fixed=yes
Remote=yes
BhaveshG wrote:
Russ,
I believe you're possibly missing the fact that (if I remember
correctly) Windows Installer only looks as major, minor and revision
(fields 1 - 3) when deciding if the version has changed... not the
fourth (typically build number) field in the product version
information.
Check the mailing
Thanks Peter and Chad!
I tried option 1. I may be interpreting this wrong, but I tried this
without sucess:
upgradeImage = newMSI (v.2002)
targetImage = rtmMSI (v.1000)
upgradeImage = newMSI (v.2002)
targetImage = sp1MSI (v.2000)
The error I get from msimsp.exe is:
Hi all,
I'd like to integrate my sandcastle generated api documentation into Visual
Studio and it seems that the VSExtension in Wix3 supports this. However I
cannot seem to get it to compile (let alone work).
I'm guessing there's something fundamental I'm missing here.
What I've done:
- Created
16 matches
Mail list logo