Hi,
I installed Visual Studio 2008 Professional Edition (Version 9.0.21022.8).
When I run Wix-3.0.2925.0.msi I get the message that Votive, the WIX project
and editor for Visual Studio, cannot be installed because Visual Studio
Standard Edition or higher is not installed.
Any ideas on why
You're better off getting one of the later releases:
http://wix.sourceforge.net/releases/
2008/6/24 Bianca Raluca [EMAIL PROTECTED]:
Hi,
I installed Visual Studio 2008 Professional Edition (Version 9.0.21022.8).
When I run Wix-3.0.2925.0.msi I get the message that Votive, the WIX
project
Hi All,
Component Id=ProductComponent1
Guid={4971CCA6-FE16-4a1d-8E03-9925F2EF85EA}
File Id='File1' Name='test' LongName='test.txt'
DiskId='1' Source='test.txt' Vital='yes'
/File
CopyFile Id='FileCopy71' DestinationProperty='DEST'
Hi,
i've got another problem. I'm using Visual Studio 2005 to develop my WiX
installer. The installer works fine, but one problem i have left is the
fact that I can't get Visual Studio/WiX to choose the right localization
files according to the language that is set. I have included all my
Hello,
For a .NET application I would like to create an event log source in
the setup process. Until moving to WiX, this was done via an
InstallUtil-type Installer class, but, for obvious reasons, I'm moving
away from this now. I have been looking at various sources of
documentation and what I've
I'll see if I can add a topic about this somewhere on my next doc refresh to
help make it easier to find. Thanks for the feedback!
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Chris Mumford [EMAIL
PROTECTED]
Sent: Thursday, June 19, 2008 6:30 PM
Bob,
I have done some more testing on this problem. I created the simplest merge
module install I could and ran it. Still gets error 1308: source file not
found. When I look in the log file, it looks like the installer is trying to
read the file it is trying to install and of course the file
Mike Rerick wrote:
I have done some more testing on this problem. I created the simplest merge
module install I could and ran it. Still gets error 1308: source file not
found. When I look in the log file, it looks like the installer is trying to
read the file it is trying to install and of
Frédéric Viollet wrote:
Could someone please tell me which condition I should use to trigger a
custom action only on installations (initial installation and minor
upgrades).
This custom action must not be run on uninstall.
See http://msdn.microsoft.com/en-us/library/aa368561(VS.85).aspx.
Andreas,
You'll need to manually build each localized version of your MSI. Votive
doesn't currently support building multiple installers per language, nor
selecting between them at build time. Here's the information from the How To:
Build a localized installer topic in our new help file:
How
It is explained in the Formatted data type description
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx).
Here is the missing File element declaration:
File Id=AppConfig DiskId=1
Name=App.cnf LongName=App.config Source=App.config
Vital=yes KeyPath=yes /
Alex Shevchuk
It's behaving as if there's a security issue on the directory. MSI will check
if the file is there because it needs to know if it needs installing or
updating. Check that the SYSTEM account has full access to WinSxS.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
The general managed code custom action mechanism depends on the shim library
InstallUtilLib.dll, so if this uses the same mechanism you need the 64-bit
version of that Dll.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory
The DTF CA's don't depend on InstallUtil.Gregory, you do seem to be
running in 32-bit mode for some reason. If you look at the MSI log when it
runs, you should have a statement showing whether it's running the 32 or 64
bit shim.
Chris
On Tue, Jun 24, 2008 at 1:52 PM, Wilson, Phil [EMAIL
I've tried this on two different machines and get the same behavior. On
both, the user was an administrator. I rebuilt the msi with 3.0.4214 and
tried it - got the same results. Both of the systems are running XP SP2.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
I am getting all kinds of broke with the latest two weekly builds as well.
I can open the solution, but it won't build the WiX project, and I am seeing
an error out of range on two of the project properties pages.
//aj
On Mon, Jun 23, 2008 at 1:21 AM, carlldev [EMAIL PROTECTED] wrote:
I can
This happens on VS2005 as well. I think it's a problem with the latest
builds.
//aj
On Fri, Jun 20, 2008 at 3:04 PM, Tony Juricic [EMAIL PROTECTED]
wrote:
Build and Tool Settings pages for my existing project in VS 2008 now
show red icon and say:
An error occurred trying to load the page.
I think this may be because the build configuration recently changed
from Any CPU changed to x86. I found the simplest fix was to delete
the solution file (.sln) and then open the WiX project (.wixproj) in
Visual Studio and let it create a new solution file.
I hope this helps.
Neil
Neil
I'm no longer using installutil: we've migrated to DFT. And we're passing in
the x64 version of sfxca.dll
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil
Sent: Tuesday, June 24, 2008 10:52 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
I suppose you could fix the bug? There isn't currently a current owner of heat
and the rest of us are fixing bugs in other areas (like candle and light) so
bugs there are pretty stale.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yaniv Cohen
Sent:
Thanks Heath, I will take a look using torch.exe, and also update the sequence
post build and see how it goes.
- Sandip
From: Heath Stewart
Sent: Monday, June 23, 2008 7:44 PM
To: Sandip Shahane; WiX-users@lists.sourceforge.net
Cc: Anandha Ganesan
Subject: RE: file sequencing
Actually, it can
I'm not sure where to look for. This is the piece that shows what platform is
used:
MSI (s) (A4:60) [16:36:38:429]: Executing op:
Header(Signature=1397708873,Version=400,Timestamp=953713811,LangId=1033,Platform=589824,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
Hi,
I've posted this issue before and didn't get any replies, so if there's a
better (MSI-specific?) place to post this, I'm happy to do that.
I'm having an issue with an installer I've created with WiX. I'm using the
latest weekly version, and before that was using a version 4 or 5 releases
Hey Ben,
The primary error message and number is different, however, the 1402 and
1450 are return values from calls to the Windows API. Take a look at my blog
entry on the 2908 error code. You might be able to track down the resolve
with that.
24 matches
Mail list logo