Hello,
the dependency walker (depends.exe) shows an error saying that, The
side-by-side configuration information in the DLL contains errors. It
fails to find the assembly DLLs (MFC80.dll, MSVCR80.dll, MSVCP80.dll)
that *are* there in the WinSxS directory.
If they are installed, maybe
I've installed WiX 3 in order to get the Visual Studio integrated version.
It works fine, and I can use sourcesafe through Visual Studio.
Now I've just started to use the UI part of WiX, it's failing, I think the
installed WiXUI library in Visual Studio is from Version 2 and may have come
with
Davut Karabay wrote:
I was thinking creating two sets of Features one for down level and one
for Vista. Then adding Conditions to each Feature for detecting OS
version, and install/not-install accordingly.
That'll work fine.
--
sig://boB
http://bobs.org
Jason Van Eaton wrote:
I have a weird bug. When installing to the default path, uninstall works
correctly. When installing to any other path, uninstall succeeds (that is to
say there are no errors) but it forgets to remove the files. Even if I have
a bug in my xml, it seems there must be
JCWrs wrote:
InstallUISequence
ExecuteAction Sequence=1 /
Show Dialog=Welcome
After=LaunchConditions/
Show Dialog=InstallLoc After=Welcome /
Show
Scott Palmer wrote:
That article indicates that Windows Installer is broken for
per-machine installs as there is no way to specify that you must have
a per-machine install that works on both XP and Vista.
ALLUSERS=1 does that. Pretend ALLUSERS=2 doesn't exist.
My ultimate goal is to
Lars Lars wrote:
Any reason why I receive these problems? The source files and configuration
is unchanged, only trying to build on another computer than the one normally
used.
A likely cause is different versions of WiX.
--
sig://boB
http://bobs.org
Hallquist Jr, Robert wrote:
I have created a WiX install of a .NET program and when it is run I
get a Microsoft Windows Error (the one that wants to send information
to Microsoft).
It's impossible to say without more details. What error do you get? If
you run the .exe from the command
Ok, I took that out, but I get the same result...no UI. I've been
trying different things (including not having an InstallUISequence at
all) the past couple of days, but nothing seems to work.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 05, 2007
Bob Arnson-3 wrote:
Why are you specifying ExecuteAction? By placing it at sequence number
1, no other UI will run before it.
--
sig://boB
http://bobs.org
Ok, I took that out, but I get the same result...no UI. I've been trying
different things (including not having an
Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
(supported on VS 2003) in order to target Wix 2.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of learnerplates
Sent: Thursday, April 05, 2007 7:54 AM
To: wix-users@lists.sourceforge.net
Subject:
Oh right,
It's Visual Studio 2005 i'm using.
Is there an editor for the WiX 2 stuff? intellisense etc, I'll probably have
to remove the Wix3 in order to get it to work with WiX 2 again!
Justin Rockwood wrote:
Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
Thanks for the response,
Actually I found out that the problem is due to one of my files that is
installed is not the correct size. The file is listed in ORCA as 204K but
when it is installed, the size is 36K. I am using a Merge Module and the
file that has problems is the first component in
Isn't that your custom action is not scheduled correctly? I mean you should
instruct the system to create a port monitor once your 'monitor file' was
extracted from msi, right?
Dacian
- Original Message
From: Friedrich Dominicus [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Are there Wix 3 versions of the UI libs?
If so how can I integrate them into Visual Studio?
Justin Rockwood wrote:
Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
(supported on VS 2003) in order to target Wix 2.
Justin
From: [EMAIL PROTECTED]
How does ServiceInstall detect that you're installing a .net service as
opposed to a regular service?
I'm experiencing difficulties installing a .net service using
ServiceInstall. The service is there but doesn't seem to be registering
properly.
How does ServiceInstall work compared to the
My apologies if this has already been answered, but I did skim all the
digests since the one this was in looking for an answer. With the caveat
that I setup the localization to the default (en-us), this works for me
(simplified here):
light -cultures:en-us -loc lang\en-us\prod_en-us.wxl -ext
I don't think there's a difference between installing a .NET service vs
. a regular service so, ServiceInstall doesn't need to detect
anything. Can you install your service with SC CREATE?
The InstallUtil.exe doesn't know a service from a hole in the ground.
All it does is look for classes
The problem is that none if the Installer methods or events are getting
called. With InstallUtil the methods and events associated with the
Installer base class are call. With ServiceInstall they are not. I would
assume that SC_CREATE would also not call the Installer base class methods.
From:
I have a Wix generated .msi file and it has been working fine for sometime
now (in English). Recently when I tried to deply on a machine that was low
on disk space I received an error dialog indicating that the machine had
insufficient space to proceed but this error message was in German. The
20 matches
Mail list logo
