Try to localize your GUIDs
On Tue, Nov 23, 2010 at 1:25 PM, Jan Gregor gregor@gmail.com wrote:
thanks
to clarify it, i use major upgrade to enable two versions to be
installed at same time (for testing purposes).
as i understand so far, i need to generate (or autogenerate with WiX)
new
Hi Kenneth,
The new visual editor for WiX was released lately and was announced here on
this mailing-list:
http://sharpsetup.eu/
Generally it consists of two plugins, one for VS 2008 and the other one for VS
2010.
From what I saw, it allows you to create quite advanced installers. I didn't
Understood. Better be safe, etc.
Thanks,
-Hernán.
El 22/11/2010, a las 15:29, Rob Mensching escribió:
It was disabled because it was generating lots of bugs. You can enable it by
setting the Harvest property to true.
On Wed, Nov 17, 2010 at 8:59 AM, Hernán Martínez
On Tue, 23 Nov 2010 08:10:33 +
Grzegorz Borczuch t-gr...@microsoft.com wrote:
The new visual editor for WiX was released lately and was announced
here on this mailing-list: http://sharpsetup.eu/
I'd be interested to know how many computers running XP will
have .NET 2.0 installed already -
Isn't the point of SharpSetup that it bootstraps .NET 2.0 when required
before running its .NET 2.0 bootstrapper/embedded UI? Also I don't think
Grzegorz was suggesting using SharpSetup as a full solution, merely as a
GUI for WiX projects.
I'd be interested to know how many computers running XP
Thanks for the info, I could overcome the problem.
But now I face other serious problems, when I try to install the msp it is
crashing and the log file gives the following error.
MSI (c) (F0:28) [08:58:20:656]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (c) (F0:28) [08:58:20:656]: Note: 1:
To answer your question, no I don't think that's possible. I think you
need at least one Component under that Feature to enable that option.
FYI Features install Components not files Components can contain more
than just files. You could try work around that by creating a
Component which
Hi,
Features are meant to be groups of functionality of your software, not
empty containers.
You should be able to restructure your feature list so that installing
just a specific feature Will be installed
on local Hard Drive will install something meaningful and work. A child
feature is usually
Pally and Dave,
Thanks for the replies...
Here is the code segment from wix file:
Feature Id=f_VDatum Title=VDatum Files Description=VDatum Files
Level=1000 Display=expand AllowAdvertise=no InstallDefault=local
Feature Id=f_EastCoast Title=East Coast Dataset Description=East
Coast
Hi all,
I have to do the following: if in the installation folder there is a
specific file, eg file.txt, then a specific file, eg mylogo.jpg should
_not_ be updated.
The installer is doing always major upgrades.
My question is: assuming that the request can be done by using a
conditional
I have a wix install with 2 custom actions. One is for a EXE and the other is
for a DLL (see below). The .EXE custom action is invoked correctly. However,
the DLL custom action gets an error 1723 (see install log snippet and source
code below).
Since others are having success with DLL
Not sure if this will help, but what I've noticed when I created C# custom
actions I saw I had to add the dll that ended with a *.CA.dll, cause I saw
visual studio creates 2 dll's in the debug or release folder for wix custom
actions.
Regards,
Henk Roos
-Original Message-
From:
Nevermind, got it working.
On Thu, Nov 18, 2010 at 4:06 PM, Simon Dahlbacka
simon.dahlba...@gmail.com wrote:
I'm trying to create an immediate custom action that would allow user
to test connection to a wcf server.
Binary Id=CaDll SourceFile=MyCustomActions.CA.dll /
CustomAction
Why not include both logos in your new msi and install only one
conditionally.
Dave
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 23 November 2010 13:04
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] If file exists, don't update
Thanks for the response.
My VS2010 is not creating 2 DLL's (what version are you using? What do I need
to do to get 2 DLL's, if that is what I am supposed to have?). However, I
created another DLL as CATestDLL2.CA.dll in my install folder. Reran install
with same results as before.
Oh I just realized you're using a different version than me. I'm using VS 2008
and wix 3.0. Sorry about that, please ignore my previous response
Henk Roos
-Original Message-
From: Pound, Robert (CDC/OCOO/ITSO) (CTR) [mailto:u...@cdc.gov]
Sent: Tuesday 23 November 2010 16:03
To: General
Hi Dave,
I can't do that. Here is the explanation: we have a product which we
release to different clients. We also have a partner with whom we
bundle, so he wants to offer our product together with his, but the logo
should stay his logo. We can't have his logo and our logo in the
installer,
Hello Everyone!
A general question that might be a bit irrelevant with this mailing list:
I previously tried configuring my whole application through WiX previously,
but eventually I realised that
This way was not maintainable, since I had lots and lots of custom action,
and custom screen etc
No. You cannot change your Component GUIDs on major upgrades blindly. You
change your Component GUIDs when the composition of your Component changes.
At that point, the new Component cannot have any overlap with any other
Component. Basically, think of Components as circles containing items
Or maybe get rid of the Feature tree and just use checkboxes?
I remember we had a problem like this in OfficeXP, in 2000 or so, and I had
to create a dummy Component that installed an empty file that we hooked up
to all Features that had no files in them to get the options on each Feature
node to
It seems to me that the answer, and path you take lies in your audience.
If you have control of your systems I expect the XP machines already
have .Net 2 because so many applications require it. This gives you
the chance to poll the path/configuration managers and learn what they
have put in
Why not give your partner a merge-module or wixlib. That way he is can
control which version of your product goes with which version of his and
it solves the logo problem
Your build consumes the same thing you give the partner and then adds
your logo
-Original Message-
From: MeCoco
That sounds good. I'm not sure I know how to do that. I learned from a
basic example and built it off of that, but I will hit the help files and
examples and find out!
Thanks,
John
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, November 23,
Hi:
I have an installer that installs files to a hidden directory.
I'm using the wix feature tree dialogue set.
After the feature dialogue has popped up, what I'd like is a dialogue to popup
showing the contents of a folder based on the feature selected. I'd like this
to happen for each feature
Are the features huge?
Why not just have east and west coast and ditch the sub features.
Simple is good, hard drive space is cheap.
Dave
-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com]
Sent: 23 November 2010 16:12
To: 'General discussion for Windows Installer XML
Hi All,
I need to disable the Repair Change options in an installer I'm working
on. However, when I enter these setting in my Product.wxs file WiX throws a
wobbly as these are already defined in the WixUI_InstallDir code.
Whats the best way to tackle this situation? Can I get at the
Hi all,
I call HeatDirectory task from a MSBuild file. When the MSBuild file is
launched from a TFS 2010 Build Server on a x64 system, it fails with the
following error:
Do a FileSearch for the specific file, and based on that property condition
your logo component to not install.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: Tuesday, November 23, 2010 6:35 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
I thought that was fixed in v3.5.2305.0. Double-check that the
wix2010.targets file is correct. You can try setting the MSBuild property
RunWixToolsOutOfProc to true as a workaround.
-Original Message-
From: Yann Normand [mailto:yann.norm...@avanade.com]
Sent: Tuesday, November 23, 2010
ARPNOMODIFY is already set for WixUI_InstallDir since that dialog set
doesn't include any feature selection dialog (so there isn't any point in
allowing Change). However, I don't see ARPNOREPAIR being set there. You
should be able to set that one property and trust the other one is set.
The code
Is it really possible to create patches using Pyro from WiX 2.0 base Setups?
I do not want to use ComponentRef's with PatchFamily element because I have
thousands of components.
Please let me know what I miss which make the patch installation to crash with
Windows Installer error.
With best
Hi:
I'm in the process of porting a legacy install to wix, and the legacy install
leave a dll registered. I need to unregister this dll and delete the directory
before continuing with my install. What is the best way of doing this?
And how can I ensure that this runs before any directories get
32 matches
Mail list logo
