Sorry, meant to say that the the comment is referring to how there is no
condition against TargetDir's value when setting the TargetDir property -- not
TargetName.
-Original Message-
From: Tony Paloma
Sent: Wednesday, March 17, 2010 12:30 PM
To: 'General discussion f
I think the comment is referring to how there is no condition against
TargetName's value (notice how most others only set the property if it doesn't
yet exist, but this one doesn't do that).
I'm unsure of what you mean by "the code snippet in the condition" because all
of the GetFullPath and Co
(and many more) are harvested from the web project but the
compiled binaries end up in the wrong folder.
Jason Stangroome
Readify | Senior Developer
M: +61 422 924 675 | E: jason.stangro...@readify.net | W: www.readify.net
-Original Message-
From: Tony Paloma [mailto:apal...@microsoft.
Can you change the "Directory ID" property on the project reference to the id
of a bin directory that you author in manually?
-Original Message-
From: Jason Stangroome [mailto:jason.stangro...@readify.net]
Sent: Tuesday, March 16, 2010 3:05 PM
To: wix-users@lists.sourceforge.net
Subject:
Votive doesn't support wildcards or variables in the include path for Compile
items. You'll still be able to build it from the command line, but you won't be
able to load the project in Visual Studio.
Newer versions of Votive in WiX 3.5 should give an error message when loading
projects using w
It looks like somehow your targets file didn't get updated. The Wix.targets
included in 3.5.1419.0 doesn't use the ProjectReferenceSourcePaths since it was
removed from the task. Previous versions of WiX had this task parameter.
When upgrading to 3.5.1419.0, did you uninstall and reinstall or ju
DLL for VS 2005/2008 and
another for VS2010, but I'm not sure yet if this is something we want to do.
-Original Message-
From: Tony Paloma [mailto:apal...@microsoft.com]
Sent: Wednesday, February 10, 2010 1:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
When a user requests to cancel a build, Votive does not stop a task currently
in progress. The build will be stopped after the current task ends. I'll look
into improving this.
Also, asynchronous building only occurs when using Visual Studio 2010. When
using VS2005/2008 the IDE will be mostly u
You should also set WixToolPath (like Brian mentioned) to where you have WiX
3.0 tools installed (which in your case seems to be C:\wix3.0\bin).
-Original Message-
From: Tony Paloma
Sent: Thursday, February 04, 2010 10:32 AM
To: General discussion for Windows Installer XML toolset
You'll need to set both WixTasksPath and WixTargetsPath. They need to point to
the WixTasks.dll and Wix.targets file respectively.
Try:
/p:WixTasksPath=C:\wix3.0\bin\WixTasks.dll
/p:WixTargetsPath=C:\wix3.0\bin\Wix.targets
Normally these files don't get installed to the WiX installation director
Have you installed the project aggregator MSI? It needs to be installed first
on systems with VS 2005 before Votive can be installed.
http://wix.sourceforge.net/releases/3.0.5419.0/ProjectAggregator2.msi
-Original Message-
From: Lynda Li [mailto:lyndali...@gmail.com]
Sent: Monday, Janua
The new build is out:
http://wix.sourceforge.net/releases/3.5.1322.0/
It should fix the problem, but let me know how it works for you.
-Original Message-
From: Tony Paloma [mailto:apal...@microsoft.com]
Sent: Friday, January 22, 2010 10:44 AM
To: General discussion for Windows Installer
The next build should include a fix for this. If not, let us know.
If you want to fix this in your current build, edit your project file in a text
editor and add "True" under your "
OneOfMyDllAssemblies" ProjectReference.
-Original Message-
From: Will Sullivan [mailto:wsulli...@softdocs
13 matches
Mail list logo
