Hi,
a big thanks for your help Neil. I've got an idea now how to manage the
language files.
Andreas Hellwig
Neil Enns schrieb:
Andreas,
You'll need to manually build each localized version of your MSI. Votive
doesn't currently support building multiple installers per language, nor
Hi,
This Wix file seems to install, at any rate all of the files get
output to the correct folder, but the ending registry edit doesn't
happen, and the installation doesn't ever stop (meaning that when I
reboot my installation is just sitting there waiting to complete) so I
have to use Windows
On Wed, Jun 25, 2008 at 10:56 AM, Baldur [EMAIL PROTECTED] wrote:
Hi Neil,
Is there anyway I can simply edit the solution files? - I'd rather do this
than recreating a complex solution that just happens to contain a WiX
project.
Notepad (or other text editor of preference) works if you
Actually it's simpler than that simply remove the wix projects from the
solution in VisualStudion and then add them back.
Everything works - including the edit buttons.
Baldur
Simon Dahlbacka wrote:
On Wed, Jun 25, 2008 at 10:56 AM, Baldur [EMAIL PROTECTED] wrote:
Hi Neil,
Is there
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=0-1079850064-1214385393=:37011
--0-1079850064-1214385393=:37011
Content-Type: text/plain; charset=us-ascii
Hi,
Where I could find some template projects to create an installer with
WIX project in VS 2008 ? Including dialogs,
Be careful, some text editors screw up the solution file. I know Textpad
for one does...
I personally use VS - I just close the solution, then use 'open file' to
open the sln file, clicking the down arrow on the Open button and
choosing 'text editor' in VS's open dialog.
Kelly
Simon
I also had the problem, that SourceControl in VS2008 is not working anymore
for the votive project and what's really annoying is that the automatic
checkout of files on edit in other projects (e.g. a C# project) is blocked by
votive.
Regards,
Dennis
Be careful, some text editors screw up the
I have a product that can be built two ways. I have two WiX installer
projects in visual studio, sharing many of the same wxs files. One project
defines a variable in the project settings to cause some of the .wxs files
to compile differently, like this:
...
Component Id=someFiles
Hey,
I'm trying to change the background bitmap and licence by setting the
following in the Product tag:
WixVariable Id='WixUIBannerBmp'
Value='D:\msiinstaller\basewxs\Images\bannrbmp.bmp' /
WixVariable Id='WixUIDialogBmp'
Value='D:\msiinstaller\basewxs\Images\dlgbmp.bmp' /
If you installed the latest weekly build of WiX 3.0 you can find several how to
guides in the help file that was installed. There's a complete sample on how to
build a simple installer, as well as examples on using registry keys. For
information on dialogs see
Hey,
I'm trying to change the background bitmap and licence by setting the
following in the Product tag:
WixVariable Id='WixUIBannerBmp'
Value='D:\msiinstaller\basewxs\Images\bannrbmp.bmp' /
WixVariable Id='WixUIDialogBmp'
Value='D:\msiinstaller\basewxs\Images\dlgbmp.bmp' /
I am just starting with WiX 3.0. As an exercise I converted one of our
simple VS 2008 setup projects to WiX 3.0 and have two questions so far:
1. How do I make the new installer uninstall the previous version of the
product? Is it just a matter of setting UpgradeCode?
2. How can I use Product
For #1 I keep forgetting that's one of the topics on my list to add to the
docs. In the mean time you can read Alex's blog entry which is how I got it
working:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx.
For #2, we have this set up as a WiX
Can you have multiple shortcuts per component?
Mine all link to the same program as the first shortcut in the component.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just
Yes, you can. If your Shortcut is Advertised then it will always point at the
KeyPath.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Burton
Sent: Wednesday, June 25, 2008 08:36
To: General discussion for Windows Installer XML toolset.
Subject:
I am searching for Notepad in 2 locations like this:
Property Id='NOTEPADEXE'
DirectorySearch Id='NotePadContainer' Path='[WindowsFolder]'
Depth='0'
FileSearch Id='NotepadFileWin' Name='notepad.exe'/
/DirectorySearch
DirectorySearch Id='NotePadContainer'
Hmm...then I'm doing something else wrong...Do they have to be advertised?
On Wed, Jun 25, 2008 at 11:52 AM, Rob Mensching [EMAIL PROTECTED]
wrote:
Yes, you can. If your Shortcut is Advertised then it will always point at
the KeyPath.
-Original Message-
From: [EMAIL PROTECTED]
No. Can you share out your code to make this a little less theoretical
conversation? smile/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Burton
Sent: Wednesday, June 25, 2008 09:55
To: General discussion for Windows Installer XML toolset.
In a project I created in VS2005 I used Installer $(Platform) as my output
name... It worked fine by created Installer x64.msi
Now, I've converted to VS2008, and it still works fine.
However, I created a new project, and set up a merge module WiX project,
with Module $(Platform) as the output
I just gave this a try with a clean Votive project by manually editing the
.wixproj file to add $(Project) to the output name and it worked fine. Here's
what my MSBuild property looks like:
OutputNameWixMergeModule1 $(Platform)/OutputName
This is with WiX 3.0.4022.0.
Can you send out what
So, here's the part where I answer my own question. Sheepishly, I have to
admit that when I changed the .wixproj file by hand, I put in ($Platform)
instead of $(Platform).. So, once that was corrected, I got the behavior I
was looking for.
The fact remains that the 2008 version seems to be
I appreciate your time, and I'm sorry you got to it before I discovered my
typo. :-\
Chris
On Wed, Jun 25, 2008 at 1:16 PM, Neil Enns [EMAIL PROTECTED] wrote:
I just gave this a try with a clean Votive project by manually editing the
.wixproj file to add $(Project) to the output name and it
Ah escaping. I'm not sure if it's a VS2008 vs. Votive thing either, but if you
want to take a test to see how painful figuring out what to escape can be, see
the following blog entries on how VS/MSBuild handle things:
http://blogs.msdn.com/msbuild/archive/2005/10/27/484742.aspx
I'd rather see it not escaped, but that's just me. I don't even know if
that's a WiX thing, or a VS2008 thing.
Auto-escaping special chars is a recent change I implemented in the Votive
properties dialogs. It is intended to prevent one from getting into a state
where the project file can't be
The GUID is NOT a *.
Component Id=Diff Guid=*
File Id=DiffFile Name=Diff.exe ShortName=DIFF.EXE
Source=$(var.Diff.TargetPath)
Shortcut Id=DiffShortcut Directory=DevPMF Name=Diff
Advertise=yes WorkingDirectory=INSTALLDIR
Icon Id=Diff.exe SourceFile=$(var.Diff.TargetPath) /
Both of your Shortcuts are marked Advertise=yes. That means they are both
pointing at the KeyPath of the Component. By default the KeyPath of the
Component is the first valid KeyPath (File, Registry,
ODBCThingIForGetBecauseINeverUseIt) child element after the Component.
-Original
So, I can have multiple shortcuts, but they will all point to the same
keypath?
On Wed, Jun 25, 2008 at 2:30 PM, Rob Mensching [EMAIL PROTECTED]
wrote:
Both of your Shortcuts are marked Advertise=yes. That means they are
both pointing at the KeyPath of the Component. By default the KeyPath
If you make the Shortcut Advertise=yes and you put them all in one Component
then yes, they will all point at the same file. You have a couple options.
Make at least one of your Shortcuts not Advertised, or put the Files in
different Components so that each of them are a KeyPath.
It worked, thank you. But now I have another problem. Lets say I have
version 1 of product:
?define ProductVersion=1.0.0.0 ?
RegistryKey Key=$(var.ProductVersion)
Now I am doing version 1.1:
?define ProductVersion=1.1.0.0 ?
RegistryKey Key=$(var.ProductVersion)
If I do upgrade
You need 'createAndRemoveOnUninstall' as the action for your key. I'm not
sure what the attribute is and I don't have a WiX project open right now,
but I'm sure somebody else will chime in or you can figure it out
yourself...
Kelly
Alex Ivanoff [EMAIL PROTECTED]
Sent by: [EMAIL
Take a look at the RegistryKey element in the WiX documentation. You can
specify the Action attribute and set it to createAndRemoveOnUninstall.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff
Sent: Wednesday, June 25, 2008 12:33 PM
To:
I tried all create and createAndRemoveOnUninstall with no luck.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Wednesday, June 25, 2008 14:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS setup
I added a dialog to my wix xml file to allow the user to input database
connection information. It's possible that the database may require an
instance name, so I included a property to store the istance name. I'm
using the following SqlDatabase element:
sql:SqlDatabase Id=Database
#2: Why not just reference the MSI ProductVersion property? Use the [] syntax
to reference properties in Registry Key, Name, or Value:
RegistryKey Key=Some\Path\[ProductVersion] /
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent:
You can, but it would be a registry search to see whether the installed flag
is set in a specific registry path. You can check with the Framework docs on
MSDN to find out exactly where the keys reside.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Can't you modify it in your C++ build? IIRC you can't manipulate strings beyond
concatenation within WiX
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Akshat Sharma
Sent: Friday, June 20, 2008 1:33 AM
To: General discussion for Windows Installer XML
I'll have to give that a shot. I'm sort of worried about modifying items in the
xml as the uninstall might not complete. Do you have any experience with it
uninstalling at all?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amy Rosewater
Sent:
This works, too, thank you. But it has the same problem of not deleting
a key during upgrade.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason
Ginchereau
Sent: Wednesday, June 25, 2008 14:56
To: General discussion for Windows Installer XML toolset.
Hi,
I guess I'll try to rephrase my question because the lack of response
probably indicates the other one wasn't phrased well, is there
anything in the following wix file that would be a sufficient
explanation for why the Registry setting at the end of the component
is never written?
If there
Warning this is a guess! Do you have the RegistryKey in a component
that has a different guid for each version? If not I can't see how the
install would know to remove the key.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
I haven't tried it, so may not work.
WiX help file is saying the following in regards Root=HKCU:
Operation occurs under HKEY_CURRENT_USER. It is recommended to set the
KeyPath='yes' attribute when setting this value in order to ensure that the
installer writes the necessary registry entries
Hi,
I used to be able to create MSI for my code and the code was moved to a
different source depot. I copied all the necessary files from the old place and
tried to build MSI and got following error message. Wonder if anybody in the
list can help me .Many thanks.
Unhandled Exception:
The component key is constant. So, you are saying to put this registry
key in its own component with autogenerated guid?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Wednesday, June 25, 2008 15:44
To: General discussion for
I would say if there is a new registry key then that is a new component
so it needs a new guid. I wouldn't say it should be auto generated as I
don't know the consequences of doing this.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
Ivanoff
Properties (including public) are NOT passed to nested installations (including
RemoveExistingProducts). Your 1.0.0 installer needs to use the
UPGRADINGPRODUCTCODE Property instead of your IS_MAJOR_UPGRADE property for
your scenario.
See http://msdn.microsoft.com/library/aa372380.aspx for more
Regarding the Vista installation issue of public properties not being
passed when the registry/domain settings are set to:
HKLM and HKCU Software\Policies\Microsoft\Windows\Installer
AlwaysInstallElevated (DWORD) to 1
Which of the following property settings is preferred?
!-- If the
Well, it is not easy in my case since this registry key has reference to
parent component. If I move this key to its own component I get linker
errors.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Wednesday, June 25, 2008 16:18
I always do the latter. There are a lot more PUBLIC Properties than you might
now and some of them could leak through data you don't need/want. Basically,
minimize attack surface.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon W
Sent: Wednesday,
Take all of the files provided in the binaries.zip or install the MSI file.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xiaoqin Sun
Sent: Wednesday, June 25, 2008 14:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] error in link using WIX
I am de-compiling a MSI generated with InstallShield 11.5. I got an error
on table CustomAction.
I also found this link to the same problem:
http://www.nabble.com/--wix-Bugs-1976057---dark-fails-on-Wise-MSI-due-to-Une
xpectedColumnCount-td17552116.html
When I look at the InstallShield
Hi,
What I'm trying to do is:
a- web site exists: add my virtual directories during install, remove
virtual directories during un-install. Keep web site during un-install (since
it existed prior to install)
b- web site does not exist: create it during install, add virtual
51 matches
Mail list logo
