The bug is opened.
http://sourceforge.net/tracker/index.php?func=detailaid=1680395group_id=105970atid=642714
--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Republic
Main +421 2 5443-5502 | Direct +421 2
Hello all,
I'm just trying to learn WiX so please excuse me for presenting a question
which has apparently been answered on this list. I just have difficulties to
understand those examples.
My problem is as follows:
I create a setup using VS2003. The installation has a dialog presenting a
Hi,
I'm a new user of wix. I'm trying to convert a setup made with Package
and Deployment Wizard of visual studio 6.
This setup use some self register dll and some shared dll wich are in
the system32 directory.
Currently, I'm using tallow to generate registry keys of self register
dll.
Hello,
I wanted to add a merge module provided within an sdk from Macrovision:
Merge Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46 Language=1033
src=Binary\installdir\isus.msm DiskId=1 / and also added MergeRef
Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46/ in a feature.
But the mergemodule isn't
Dark has never been a proper decompiler. It works for the most part, but it's
basically in there so
you can open up existing MSIs and find out what's going on as a starting point.
The WiX team have
always said that you shouldn't expect a dark'd MSI to compile.
Rob
Lasse Rantanen wrote:
Is the DLL shared just between your products or with other parts of the system?
You're not really
meant to put things in the system32 folder.
Rob
Jacquet Fabian wrote:
Hi,
I'm a new user of wix. I'm trying to convert a setup made with Package
and Deployment Wizard of visual studio
I'm guessing that Jacquet's app is written in VB6 and probably uses some
DLLs that Microsoft provide. In which case, the files probably should go
in system32, as they may already be installed...
I'm in a similar situation - preparing to write my first WiX install,
for a VB6 app. I'm guessing
OK,
Thank you Rob - everyday you learn something. So I forget this approach.
Lasse
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions
It's exact. I have to install the VB6fr.dll which is the vb runtime.
I discover I have another problem too. I have to register an activeX which is a
.exe
Could I do this with tallow?
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Thomas Leigh
Envoyé :
Also Is there a reason that each file is in its own fragment? That
really isn't that big of deal I guess, it just seems like it would be
easier to read if they were grouped together.
That's the default; you can override it with -sfrag. The advantage of
many fragments is that each is separately
Scott Sam wrote:
Sorry if these is are stupid questions, but if there are better ways
to do things than the way I am currently, I'm quite interested in
learning them. Linkable to what? If you link in the fragment do you
still have to make the component reference? What is the advantage of
Thanks for answering my questions. That makes sense now. Heat creating
the componentgroup would be very helpful to me. What version/build is
it in?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 10:53 AM
To: Scott Sam
Cc: wix-users@lists.sourceforge.net
Subject:
In our product, we have a bunch of features that are usually all
installed on the same machine, but were designed to be able to be
installed as stand alone programs on separate machines. As a result,
there are a bunch of files that are shared between the different
features. Currently I have all
Put any components that can be shared into a shared folder. The just list the
required components
under whichever features need them. It's OK to have components under multiple
features. Windows
Installer will take care of it for you.
Rob
Scott Sam wrote:
In our product, we have a bunch
Scott,
If I understand you correctly, you are saying that you currently have
the same source file included in multiple components. Is that right?
If so, presumably there is something stopping you from putting the
file(s) in as many components as you need and including a ComponentRef
to
Thanks Justin-something else that I just noticed was that if you're
working with a library project, you can't add a reference to it in an
installer: you need to reference the compiled wixlib directly. This
works, but if it's possible to reference the project directly (so the
linker will use the
Re: FASTOEM
I read the same requirement and found details on what is required for this
functionality to work here:
http://msdn2.microsoft.com/en-us/library/aa368576.aspx
So, it could be something as simple as the package not been ran from the
same volume... when it does work, it goes lightning
I've done something similar, but while I don't have a solution to your
'double-click Next' issue, I can suggest how my validation works.
On the 'Next' control button I have a pair of Punlished Events for
true/false as you do, but only one is NewDialog. The
REGISTRATIONCODEVALID=false case
What version of the WiX toolset are you using?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Duohong Xia
Sent: Tuesday, March 13, 2007 5:33 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SchedXmlFile: Error 0x8007007a: failed to copy value:
I'm working on a mini-document that talks about CustomAction best practices
that I'll eventually post on my blog (lots of stuff to cover). I haven't seen
anything that talks about good ways to organize WiX source code.
What do other people do?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
The merge would have failed horribly if it wasn't a Merge Module. It looks
like dark got confused and tried to decompile your Merge Module as a Product
and that is why the Product element is completely blank.
I expect the reason it didn't install is something to do with the install
itself.
You should never ever package someone else's resources in your installation
package. If you do that then your install will take ownership of the resources
and mess up everyone. Definitely use a Merge Module. VB6... hmm, might be
hard to find stuff for that.
Also, don't install your
We've tried to get a bit better in WiX v3. Still may need more work, but WiX
v3's dark is much better.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
Sent: Wednesday, March 14, 2007 2:39 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
Personally, I ...
* Use 4-space indenting on any child
* If the attributes get to unwieldly to have on a single line, I put each
one on a separate line, indented 8-spaces from the tag start.
* I match the indentation of the close tag with the open tag.
A snippet:
Julie
[EMAIL PROTECTED]
(Continued, sorry, hit the send key accidently)
Directory Id='TSBDIR' Name='Test Script Builder'
Component Id='TSB' Guid='0B3BEB7B-7822-498F-A599-F4509514FE45'
File Id='TestScriptBuilderEXE'
Name='TestScriptBuilder.exe'
Re-arrange the code a lot :) If you want to save yourself a lot of effort,
scribble down a rough
idea of where the WiX files are going to be, and where they're going to get the
product files from.
Then work out what needs to be done in when you want to change a product file
to a new
Hello,
I am trying to register a .net dll using regasm. I have used regasm to create
a registry file and then used tallow to convert the registry file to a .wxs
file. I am using wix version 2.0.4415.0. However it doesn't seem to create
all the registry entries. Am I missing a step? Also, I
This was my suspicion, I tried with CD simulation software with the same
result.
Maybe I need to try with real CD.
Do I have to define VolumeLabel attribute for MediaTag in this case or it's
optional?
Thanks a lot
Igor
Bob Arnson-3 wrote:
Igor Maslov wrote:
Error 1311. Source file not
Thanks. I didn't realize you could have the same component in different
features. That should solve the problem.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
You we're right, MSI was thinking that some other client was using this
product.
Ive found out that those were the common reg entries generated by Tallow.
The more i use Tallow, the less i like it :(
So i got rid of the non-component-specific entries made by tallow, and now
it works correctly
In the project I'm working on, we've hit a pain point and we're not
certain how to overcome it. Right now if we want to do an upgrade, the
user has to uninstall before installing the new version.
I am sure this has to be possible, I just need some pointers on the how
to side of things.
That should work. If you have any custom actions in your msm verify
that the sequencing is after the cost standard actions.
Thanks,
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoff
Finger
Sent: Wednesday, March 14, 2007 1:04 PM
To:
I am trying to run an application at the end of an install. The application
needs files that are installed as part of the install and they need to be in
the same directory. The CustomAction line I have is:
CustomAction Id='LaunchFile' FileKey='install_silent.bat' ExeCommand=''
Does it complain about a different version of the product already being
installed? If so, you need to install the MSI via the msiexec.exe command
like this:
msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus
On 3/14/07, Rory Clark [EMAIL PROTECTED] wrote:
In the project I'm
That solved the short term problem, but isn't a long term solution.
Looks like I need to do a lot more research and a lot more reading.
Thanks!
Rory
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:39 AM
To: Rory Clark
Cc:
What are you trying to achieve? Are you trying to make it so you don't have
to do that from the command-line? One thing that I think that you can do is
set a property in your wxs file that is:
Property Id=REINSTALLMODE Value=vomus /
If you look at the MSDN documentation for the REINSTALLMODE
Rory,
One thing to be aware of (which caught me, and continues to be a source
of frustration from time to time) is that Windows Installer only looks
at the first 3 parts of the version information.
Lesson 4 in the tutorial (http://www.tramontana.co.hu/wix/lesson4.php)
should offer some
There is also the option of major upgrades that don't require command-line
parameters at all.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson
Sent: Wednesday, March 14, 2007 12:13 PM
To: Rory Clark
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Help with
Rob,
Is there a short answer as to why you're not supposed to set the
REINSTALLMODE property to vomus and just leave it like that?
On 3/14/07, Rob Mensching [EMAIL PROTECTED] wrote:
There is also the option of major upgrades that don't require
command-line parameters at all.
*From:* [EMAIL
Can I set the desktop to point to all user?
By using DesktopFolder, I can only set it to point to the per-user.
Thanks,
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll
I believe the ALLUSERS property needs to be set to 1
On 3/14/07, Bei Liu (Volt) [EMAIL PROTECTED] wrote:
Can I set the desktop to point to all user?
By using DesktopFolder, I can only set it to point to the per-user.
Thanks,
Set the ALLUSERS property to 2. That should do it.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu
(Volt)
Sent: Wednesday, March 14, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Set All Users
v means any time you do a repair operation with the MSI, that the original
source media will be required. Users *hate* that.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 12:23 PM
To: Rob Mensching
Cc: Rory Clark; wix-users@lists.sourceforge.net
Subject: Re:
I thought that the v will run from the source (the msi that you're
currently trying to install) and recache the local copy. When would it ask
for the source media?
On 3/14/07, Rob Mensching [EMAIL PROTECTED] wrote:
v means any time you do a repair operation with the MSI, that the
original
I'm trying to make some code that installs only on Windows:
XP SP2 or better,
2003 SP1 or better,
or Vista or better.
I'm using the code below, and my application happily installs itself on Win2000.
What am I doing wrong?
Property Id=WIN2KSP4EXISTS![CDATA[VersionNT = 500 AND
I don't believe you can set properties like that. Instead, use your
VersionNT=... conditions inside the Condition / element. That should
work.
On 3/14/07, Nick [EMAIL PROTECTED] wrote:
I'm trying to make some code that installs only on Windows:
XP SP2 or better,
2003 SP1 or better,
or Vista
You could be right. I haven't played with setting v all of the time, so I'd
have to create a few MSI files and do that.
Now that I finally did all the work to show why COM advertisement is bad and
why ICE33 can be ignored
I'd be interested in seeing your solution, Peter. Can you post your solution
on the Wix-users list for future reference? I feel this shouldn't be hard,
but if you already have it, then why reinvent the wheel!
Thanks in advance.
On 3/13/07, pobox77 [EMAIL PROTECTED] wrote:
Thanks Dana,
I've
It looks like that Directory element doesn't have an attribute called
ALLUSERS.
Directory Id=DesktopFolder Name=Desktop AllUSERS=1/
Is there any other way do set it?
Thanks,
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 12:51 PM
To: Bei Liu (Volt)
Cc:
ALLUSERS is an installation level property. (I.e. you can run the
installation for the current user - ALLUSERS = 0, or for all users -
ALLUSERS = 1). It is not associated with the directory.
Beware - the property is a public one, and therefore needs to be all
uppercase.
You really don't
Those properties won't be evaluated at runtime. Instead, they'll be set to
the specified text. The expression in the Condition element will then be
evaluated as
VersionNT = 501 AND ServicePackLevel =2 OR VersionNT = 502 AND
ServicePackLevel =1 OR VersionNT 502
The condition evaluation treats
Is there a WIX MSBuild task? I have the Wix target file and assembly
(version 2), however the only example I can find imports the wix target file
and immediately builds, and doesn't do anything else I have specified in my
build script. Is there a WIX task I can call from within an MSBuild
Hello,
I'm not sure if I'm phrasing this correctly but I'll throw it out there
anyway...
Is there any way with Wix to pick up new tables in the Windows Installer
4.0 msi schema? I'm particularly interested in the MSIPatchCertificate
table.
Thanks,
Tom
Yeah, changing the sequence of ResolveSource from 525 to 1025 fixed it, thanks!
Is there a way to override the sequence of an item in a Merge Module
when you reference it, or am I going to have to run Orca and fix it
manually every time I recompile?
On 3/14/07, Thomas Svare [EMAIL PROTECTED]
I would like to know if there is a way to make a custom feature selecion
control.
Or at least, how to put and checkbox and enable or disable a particular
feature.
I browse wix code but find anything.
Thanks,
Brian J. Cardiff
You should be able to set the sequence of the offending custom action
from the msm in main WiX project I think.
Thanks,
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoff
Finger
Sent: Wednesday, March 14, 2007 4:21 PM
To:
Visual Studio 6.0 SP6 merge modules are downloadable from
http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-48cf-
bb4e-3aec65edd50bdisplaylang=en. Note the bugs listed at
http://www.installsite.org/pages/en/bugs_msi.htm#wimsm (scroll down past the
extremely well documented
I guess I just thought that 2 was more appropriate as a general setting
because it doesn't cause an error during installation if the user is not
running as an admin. If sending the shortcut to the all-users desktop is
critical to the installation, than ALLUSERS=1 would indeed be better. I
guess I
There is no mechanism provided by the mergemod.dll to resequence CustomAction
order. ResolveSource is one of those CustomActions that can live in many
places... it sounds like the Merge Module isn't respecting that. You best bet
is to not have it in the MSM at all. ResolveSource can cause
Is there a way to intercept SQL install errors and display my own custom
error(s)?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
In v2 you used to be able to add custom bitmaps to the Dialogs.
Has that changed in v3 or am I doing something wrong.
I created a Sub-Directory called [Bitmaps] and added my own files for
bannrbmp.bmp and dlgbmp.bmp. But when I compile the solution it doesn't
override the bitmaps.
Ryan
Follow the rules recently discussed for the license. The variables are:
WixUIBannerBmp
WixUIDialogBmp
WixUIExclamationIco
WixUIInfoIco
WixUINewIco
WixUIUpIco
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Perlman
Sent: 14 March
How would I set a registry value to:
$(hClientWnd) $(Node) $(DBUserID) $(ConnectionString) $(Product)
PackageReport ChangeDoc [EMAIL PROTECTED]
If I use this:
$(hClientWnd) $(Node) $(DBUserID) $(ConnectionString) $(Product)
PackageReport ChangeDoc [EMAIL PROTECTED]
Candle returns this error
Yes. Provide a .wxl file for the localization identifiers defined the .wixlib.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Wednesday, March 14, 2007 3:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Intercepting SQL errors and displaying
Mike, Rob,
Thank you both. I should have thought of v3.0 but I just can't stop
using v2.0 for quick test purposes.
Thanks,
Tom
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 5:09 PM
To: Mike Dimmick; Thomas Svare;
You need a Custom Action Type 34 to run an exe with a working directory.
Try this:
CustomAction Id='LaunchFile' Directory='INSTALLDIR'
ExeCommand='[INSTALLDIR]install_silent.bat' Return='asyncNoWait' /
K-ballo.-
Charlie Grosvenor escribió:
I am trying to run an application at the end of an
Igor Maslov wrote:
Do I have to define VolumeLabel attribute for MediaTag in this case or it's
optional?
It's required -- see the MSI doc on the Media table, VolumeLabel column.
--
sig://boB
http://bobs.org
-
Take
Brett Kapilik wrote:
I guess I just thought that 2 was more appropriate as a general
setting because it doesn't cause an error during installation if the
user is not running as an admin. If sending the shortcut to the
all-users desktop is critical to the installation, than ALLUSERS=1
would
Brian Cardiff wrote:
I would like to know if there is a way to make a custom feature
selecion control.
Or at least, how to put and checkbox and enable or disable a
particular feature.
MSI doesn't support custom controls but you can make a custom dialog
with checkboxes and use AddLocal and
Ryan Perlman wrote:
Has that changed in v3 or am I doing something wrong.
Yes, it changed. See WiX.chm topic Using the WixUI dialog library for
details.
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash.
Thank, for the previous pointer by Mike Dimmick
For anyone else that may come across this issue:
If you are compiling via the command line you can use the syntax,
-dWixUIBannerBmp=path-to-banner-bmp
If you are using this with your MSBuild environments or through the Visual
Studio *.wixproj
71 matches
Mail list logo
