It's been a while since I've touched Votive 2 code so my memory may be hazy,
but I don't think Votive 2 is supported under VS 2008. It's designed for VS
2003/2005. If you want to use VS 2008, I recommend upgrading to Votive 3.
Even if Votive 2 works under VS 2008, there has been so much added to Vo
This looks like a Votive bug and not a configuration issue. Please log a bug
for this on the SourceForge site:
https://sourceforge.net/tracker2/?group_id=105970&atid=642714
Thanks,
Justin
-Original Message-
From: David KILLICK [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008
Unfortunately .vcproj references aren't supported because they're not
MSBuild compliant. There is a feature request out there to add this support,
but my guess is that it won't happen for a while. Sorry. :(
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beh
I believe that WiX should just work with TFS since we use MSBuild.
Admittedly, I haven't tried TFS builds before, but from what I understand,
they're also driven by MSBuild. My guess is that you're not defining
$(WixTargetsPath) early enough - you before defining $(WixTargetsPath). If that's the c
Please report bugs for both of these issues. They're separate issues. For #1
are you adding the .wixlib as a reference or the project that builds the
.wixlib as a reference (one is a file reference the other is a project
reference)? The code is slightly different between the two, which is why I
ask
Make sure you're using WiX version 3 and from the drops at
http://wix.sourceforge.net/releases. I think it should work for you then.
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon Drnek
Sent: Wednesday, June 18, 2008 12:45 PM
To: wix-users@lis
Votive does not do any conversion. We tried to get all uppercase letters for
the GUID, but Visual Studio automatically generates those when it creates
the project templates. There may be a way around it by using the Wizard
infrastructure, but it was a low priority item.
Justin
-Original Messa
Can you explain what you mean by "proper GUIDs"? I wasn't aware that Votive
was generating bad GUIDs.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Shevchuk
Sent: Thursday, June 12, 2008 3:35 PM
To: General discussion for Windows Installer XML
Are you having these problems in VS 2005 or VS2008? The code is different
between the two, so it really helps us if we know which version. I assume
it's 2005.
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Colin Bleckner
Sent: Tuesday, June 03, 20
you don't
have to deal with it.
Don
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Wednesday, May 14, 2008 9:43 PM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with
earlier builds
Interesting discussion so far. I just wanted to chime in a little here. I
think Mathias is correct here in stating that there are some real problems
with Windows Installer (and thereby Wix in its current form). I work on the
dang thing but I still get frustrated at Windows Installer. It's just too
ones that should have
higher priority (along with the other one that you pointed out - same line
output). Thanks for the bug reports!
Justin
From: Scott Palmer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 14, 2008 7:14 AM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net
Subject: Re
The long lines in VS 2005 has been around for a while. This is due to a bug in
Visual Studio 2005 that was fixed in Visual Studio 2008. There are some ways
around this bug, but none of them are pretty. We'll have to take another look
at it and see what we can come up with.
Justin
From: [
I hate the locking as well. Unfortunately, this is a bug in the MPF (the Visual
Studio SDK) that they have not fixed yet. We will have to just fix it on our
own instead of waiting for a fix from them. Note that it's not a trivial fix
either because it requires a separate thread to do the build.
The 4 registry errors are known and "normal". NAnt issues errors when it
can't find the registry key even when we have failOnError="false" in the
NAnt files. If you know of a way to get rid of those non-fatal errors we'd
gladly take the fix. I've gotten used to seeing the errors, so I just ignore
t
It's been so long since I've looked at Votive 2.0, but I seem to remember
that it doesn't support it. Just a note that Votive 2.0 was more of a
preview release and we disbanded support for it when we moved to Votive 3.0.
Before Christopher Painter jumps in and tells us that this is a bad customer
s
Wix 2 and 3 can co-exist if you don't install Votive (the Visual Studio
plug-in). If you intend to use Votive, then you need to uninstall the
previous version of WiX before you install a new version. However, you can
use Votive 2.0 and Votive 3.0 side-by-side if you have both VS 2003/2005 and
2008
Unfortunately, this is expected behavior. Votive does not support
non-MSBuild project references, of which VC++ is one. We considered adding
this support, but it's a big work item and haven't gotten around to doing it
yet.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf O
Unfortunately, this is expected behavior. Votive does not support non-MSBuild
project references, of which VC++ is one. We considered adding this support,
but it's a big work item and haven't gotten around to doing it yet.
Justin
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ry
ild.
Justin
From: Robert O'Brien
Sent: Wednesday, April 09, 2008 6:06 PM
To: Justin Rockwood; Jason Ginchereau; 'wix-users@lists.sourceforge.net'
Subject: RE: [WiX-users] is there a way to access wixproj macro values from
within wix sources
Fyi - I just updated
Sounds like a nice thing to have. Would you mind logging a feature request
including the text of your message (you explained it very well)? You can do it
here:
http://sourceforge.net/tracker/?group_id=105970&atid=642717
Thanks,
Justin
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
In one of my last blog posts
(http://blogs.msdn.com/jrock/archive/2008/02/13/changing-the-file-extension-
of-wix-extensions-from-dll-to-wixext.aspx) I wrote about how we would be
changing the file extension of WiX extensions from .dll to .wixext. Well, it
turns out that we won't be doing it for tec
I'm not sure what Christopher is intending with his tone here, but I don't seem
to remember anybody being opposed to doing anything that the community wants to
do. It's just all a matter of time and resources. If the community would like
to have a forum, I don't think anybody is opposed to it. S
We will be doing a change that will probably affect most users of WiX v3, so
I wanted to get this notice out in the community to notify people of the
upcoming change. Within the next few weeks we will be changing the file
extension of WiX extensions from .dll to .wixext. There are several reasons
w
me again. :)
Justin
-Original Message-
From: mark.modrall [mailto:[EMAIL PROTECTED]
Sent: Friday, February 01, 2008 11:42 AM
To: Justin Rockwood; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] pre-defined variables?
Hi Justin...
Still doesn't seem to work... At lea
s is a 3.0-only thing?
Thanks
Mark
-----Original Message-
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 6:03 PM
To: mark.modrall; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] pre-defined variables?
I also just blogged about this, so you can c
I also just blogged about this, so you can check out
http://blogs.msdn.com/jrock/archive/2008/01/29/complete-list-of-candle-prepr
ocessor-variables.aspx.
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of mark.modrall
Sent: Wednesday, January 30, 2008
There's a complete list in wix.chm. Here's the list again if you need it:
Project References
Introduction
The WiX Visual Studio package supports adding project references to a WiX
project. This ensures that build order dependencies are defined correctly
within the solution. In addition, it
Relative references should work if you hand-edit the .wixproj file (let me
know if they don't). We fixed a bug recently where the UI portion of it
would write out the absolute path, but I don't know if it's in the latest
build or not.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
n the
meantime, we also have a bug logged against Votive to fix this, so we may
get to a fix before it's fixed in the MPF.
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 21, 2008 11:24 AM
To: Justin Rockwood; 'Ryan O'Neill'; wix-users@lists.sourcefo
There are several bugs logged on this already. It broke a few builds ago and
the fix isn't in the build yet. It should work again soon. Sorry about the
hassle.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan O'Neill
Sent: Sunday, January 20, 2008 6:15 AM
To: wix-u
Yes, it was broken by a recent check in somebody made. The bug has been
fixed and should be resolved by the next drop. Sorry about that.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Wednesday, January 16, 2008 7:10 AM
To: lgntt; wix-users@l
Yes, it looks like we have a break. So sorry about that. We've been taking a
look at the issue and hopefully will have a fix for this week's build.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Tuesday, January 15, 2008 10:46 AM
To: wix-users@l
If you're using Wix v3, we have all of these detections wrapped up in an
extension so you don't have to duplicate the effort. They're contained in
the WixVsExtension.dll. If you need a reminder on how to use an extension,
check out
http://blogs.msdn.com/jrock/archive/2007/10/19/how-to-use-extension
RE) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 19, 2007 7:19 PM
To: Justin Rockwood; wix-users@lists.sourceforge.net
Subject: RE: Having trouble with Wix V2 (title change)
Installing 1.1 SDK and .Net 3.5 fixed the build issue. Thank you.
However Votive still does not work. I am using Votive-
Which version of Votive are you trying to use for your first problem? It was
unclear whether you're using v2 or v3.
As far as the build failures go, Wix 2.0 requires the .NET Framework 1.1 SDK
(which is different than the runtime). You're right in that the runtime is
installed with the OS, but
Thanks for your feedback and for the bug. We actually already have a fix for
that underway, so it should be in the builds fairly soon.
Justin
-Original Message-
From: si [mailto:[EMAIL PROTECTED]
Sent: Monday, December 17, 2007 10:09 PM
To: Justin Rockwood
Cc: WiX Users; Candy Chiang
We'd like to change the file extension for WiX extensions from .dll to
.wixext, but wanted to get a feel from the community how this would affect
people. Please respond if this would affect you negatively (or positively)
and how. Note that this is just for wix v3. Version 2 is not affected.
Jus
Sorry for the delayed response. Yes, the project reference variables were
added back to Votive 3, so they should work just fine for you now.
Justin
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 6:54 AM
To: Justin Rockwood; WiX Users
have 2008
installed you won't see the option for 2005).
Thanks,
Justin
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Friday, December 07, 2007 12:40 PM
To: Justin Rockwood; WiX Users
Subject: RE: [WiX-users] Votive on VS 2008?
No, I'd grabbed the l
Have you picked up the most recent version on
http://wix.sourceforge.net/releases (Votive 3, not 2)? Aaron has already
done the work to get Votive to work with VS 2008 Beta 2 and I hear that it
works on RTM as well. We're actually finishing up a change that will use the
RTM bits as well, but I thin
This is a known bug and we're working on a fix. It's actually a bug in
Visual Studio 2005 and not in our stuff, but we're working to get a fix for
it. It works fine in Visual Studio 2008. Also, the task pane should show the
errors in the correct format in both versions as a workaround.
Thanks,
Jus
rd [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 25, 2007 2:50 PM
To: Justin Rockwood
Cc: Dong Fang Xie (Excell Data Corporation); wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Some STUPID Limitations in WiX
Hi Justin:
Even though your advice and comments to Dong are 100% correct
et
Subject: Re: [WiX-users] Some STUPID Limitations in WiX
I have seen this time and time again. When someone doesn't understand the
subtle nuances of the Windows Installer service, all of a sudden all the
tools built around it suck or are "STUPID". :-)
On 9/25/07, Justin Rockw
Hey, Dong, thanks for the laugh! :) While we appreciate feedback on the WiX
toolset, it's typically not a good idea to call it STUPID and then in the
same sentence ask for help. You're biting the hand that feeds you. Plus if
you think it's stupid then why would you trust the advice from the people
You're right that what you want is dangerous because it goes against
component rules. However, I can also see the value in having something like
this inherent in Votive. If you want to log a feature request, I think it
would be something good to add to Votive. I'd probably have some sort of
scary d
This bug has been fixed, but hasn't been checked in yet. In the meantime,
you can make the change yourself if you want (the change is in bold):
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Dierkes
Sent: Wednesday, September 12, 2007 1:40 AM
To: wix-users@
Sounds like your wxs file is not saved in UTF-8 or some other encoding that
allows German characters. Also, you have to have at the top of your XML file.
Justin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of pobox77
Sent: Monday, September 10, 2007 1:2
To get back to your original question where you're setting $(WixToolPath) to
point to the 2.0 versions. That should work fine unless you try to pass in
arguments that only the 3.0 versions support. I don't remember off the top
of my head what those new properties are, but you'd probably learn prett
Unfortunately, there's a bug right now in wixlib references. You can
manually add the reference (not a project reference) and have it work fine.
Like you said, though, I think it stores a hardcoded path, which is a bug.
Adding a .wixlib project reference, however, does not currently work as
expecte
You can do one of two things:
1) If you're deploying DLLs that you build within your Visual Studio
solution, then you can use the project references to do it. Right mouse
click on your Votive project and click "Add Reference". Then add a Project
Reference to the DLL that you want to deploy
line that may cause this error?
The file is where it is looking for it, i have tried absolute paths as well.
thanks
_
From: "Justin Rockwood" <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2007 9:50 AM
To: "'steve baker'" <[EMAIL PROTECTED]>,
Sub
There are actually two bugs here (or NYI features, however you'd like to
view it J). The first bug is that Votive (.wixproj) projects actually don't
work with project references right now (meaning that you can't have a
project reference to another wixproj and have it generate the preprocessor
varia
Yes, there are plans to add designers to Votive. It's been on my list for a
while, but unfortunately my spare time has been rare the past few months. I
think the first designers will probably be very basic and rudimentary (I'm
thinking of registry and file/directory editors), but eventually more wi
It depends on what build you're using. I recently checked in a fix (a couple
of weeks ago) where some property changes would not mark the project as
dirty, so they wouldn't save. I think things should be working now, though.
Let me know if you find that you're still having problems with changes not
It might be better to just use preprocessor variables in your WiX files and
then pass in those values when you call the MSBuild NAnt task. In your wxs
files use:
$(var.Version) and then when calling MSBuild, set
/property:DefineConstants=Version=1.0.1013.0. Then you don't have to use
NAnt to change
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: [
6:04 AM
To: Justin Rockwood
Subject: (votive, wix, vsip, and all things microsoft) : Changing licence in
Votive
Importance: High
Hi,
sorry for taking this way of communication but I couldn't find the anwser to my
question elsewhere.
Is it possible to change the license agreement shown in the
ony Wieser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 3:07 AM
To: Justin Rockwood; wix-users@lists.sourceforge.net
Subject: Problems with Dependencies inVotive
I've added this to my project:
dude.cab
When I reload the project in vs2005, this is what ends up in t
You guys are absolutely right. I'm so sorry for leading you in the wrong
direction. I'm an idiot. J I forgot that I hadn't fully implemented the Link
feature yet. I'm sorry about that. I think, though, that you should be able
to manually tweak the .wixproj file to make it work, although I haven't
a
Although the feature to use $(var.Project.TargetPath) isn't done yet, you
can still do what you want by using MSBuild variables. In your .wixproj
file, add the following to a element:
Configuration=$(Configuration)
This will automatically add the -dConfiguration=Debug to the candle command
l
D]
Sent: Friday, March 23, 2007 2:15 PM
To: Justin Rockwood; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies
inVotive
Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies
inVotive
> In Visual Studio, when you
ly, you have to do this:
How you want the file to appear in your project
A more concrete example:
MyExe.exe
You shouldn't get messy directory structures if you do this approach.
Justin
-Original Message-
From: Anthony Wieser [mailto:[EMAIL PROTECTED]
Sent: Friday, Mar
Do you mind logging a bug on the _TimeStampAfterCompile? I'll look into
that.
As far as forcing a recompile... You can do that by including your inputs
into your .wixproj project file as elements. In Votive, you do
this by selecting "Content" from the Build Type property in the property
browser (
There aren't any plans to add explicit support for Votive in Orcas until
Orcas actually ships. I've got too much other stuff on my plate right now to
add support for another platform. J Sorry about that.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peli de
Halleux
S
There aren't any plans to add explicit support for Votive in Orcas until Orcas
actually ships. I've got too much other stuff on my plate right now to add
support for another platform. J Sorry about that.
Justin
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peli de Halleux
Sent:
Yep, I'm "close" to having it back. :) For now, you can just define those
variables yourself and pass them into the command line. If you're using a
.wixproj with MSBuild/Votive, then you can define them in the
property variable. In Votive, the property pages will give
you access to that prope
Good points. I don't necessarily like defaulting to en-US, just because WiX
is being used quite heavily in other locales (German, Russian, and Dutch are
ones that come to mind). However, defaulting to the OS culture makes a lot
of sense. Let me know if you have any other suggestions as you dig more
Do you mean adding the wxl file or the wixlib/wix extension (dll)? I notice
that this experience is perhaps not the most intuitive. Any suggestions on
how I can make this more obvious or easier to discover in Votive?
Thanks,
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behal
Soon, soon, I promise. J I've been working on it, but need to set aside some
time to finish it up. And yes, I'll put them into the chm file as well. Good
suggestion.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
Dahlbacka
Sent: Thursday, February 22, 2007 1:23
Soon, soon, I promise. J I've been working on it, but need to set aside some
time to finish it up. And yes, I'll put them into the chm file as well. Good
suggestion.
Justin
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Dahlbacka
Sent: Thursday, February 22, 2007 1:23 PM
T
me know.
Justin
From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 12:47 PM
To: Justin Rockwood; 'Mark Capaldi'; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive - Adding File as a Link
If you edit the project file directl
It's one of the things on my list to do, but linked files do not currently
work yet. Sorry about that.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Capaldi
Sent: Thursday, February 08, 2007 6:10 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Votive
You can edit that property () in the property pages if
you're using Votive. Just right mouse click the project in Solution Explorer
and click "Properties." Alternatively, you can edit the .wixproj file
directly and add Name=Value;Name2=Value2
within an existing . Make sense?
Justin
From: [E
I haven't played around with Ankh to know, but other users have run into
issues with this also. I really don't think it's a Votive issue, since I'm
using the standard Visual Studio SCC stuff. I really think it's an Ankh
issue. Of course, I could be wrong. It's probably best to log a feature
request
I may be wrong, but I seem to remember that Win2003 only comes with .NET
Framework 1.1 and not the service packs. Have you tried installing SP1?
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters
Sent: Tuesday, November 21, 2006 9:50 AM
To: 'Wix Group'
Subje
es of the .wixproj in the linker tab, there I can
set userdefined variables, there I added
"Configuration=$Configuration" but even then, I can not access this
variable like above inside my WiX-code.
Oliver
From:
Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent:
The variable $(Configuration) is set by most MSBuild scripts
automatically (C#, VB, VJ#, WiX, etc.). Also, $(ConfigurationName) is usually
set as well, but I’d probably go with $(Configuration). You won’t be able to
know what the configuration is outside of MSBuild, but assuming that you’re
: Monday, November 06, 2006 5:23 PM
To: 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
itenterprise ready?
Hello Justin!
Thnx for this list of references it is really very helpfull to me.
: Monday, November 06, 2006 5:23 PM
To: 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
itenterprise ready?
Hello Justin!
Thnx for this list of references it is really very helpfull to me.
Here are some of the Microsoft products and groups that use WiX for their
installations:
* Office 2007
* Office Server 2007
* Windows SharePoint Server
* SQL Server 2005
* Visual Studio
* Windows Defender
Additionally, there are several non-Microsoft products that use WiX. The
biggest one that co
Or you can just use the built-in wix.targets file that we ship with wix.
That will do all of the right stuff for you, including smart incremental
builds. If you use Votive v3, you'll automatically get MSBuild projects, but
you don't have to use Votive to still use the wix.targets file.
Justin
---
Title: Custom Action in Merge Module
Glad to hear it! I put a lot of work into getting Votive v3 to
be much improved over v2, so I’m glad that it’s getting there. There’s still a
long way to go to make it really, really nice, but it’ll get there eventually. J
Thanks,
Justin
Fro
Those are all great comments and suggestions. Would you mind
filing three feature requests at http://sourceforge.net/wix?
Thanks,
Justin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Suraj
Barkale
Sent: Wednesday, September 27, 2006 4:23 AM
To: wix-users@lists.so
All of the issues have (hopefully) been fixed and the new build should be
good to go. You can find it at
http://wix.sourceforge.net/releases/3.0.2120.0/Wix3.msi. Let me know what
you think!
Thanks,
Justin
-
Take Surveys. Ear
Thanks for your input. Votive is one of two things that are a
stumbling block from last drop. Please be aware, however, that Votive went
through a major overhaul, and thus there are some “growing pains”
for the first drop. Also note that Wix v3, although very stable, is still a
beta version
m too, but no I didn't have an instance of Visual
Studio Open at the time of Installation.
Justin Rockwood wrote:
>
> When you installed Votive3.msi, did you have any instances of Visual
> Studio
> 2005 open? If so, please uninstall and reinstall without them open. If
> not,
esday).
Unfortunately the only workaround is to install the Visual Studio SDK so
that the DLK is installed and will override loading the package using the
PLK.
Justin
-Original Message-
From: Pete Skelly [mailto:[EMAIL PROTECTED]
Sent: Monday, September 18, 2006 1:00 PM
To: Justin Rockwood
Su
onday, September 18, 2006 6:58 AM
To: Justin Rockwood
Subject: Re: [WiX-users] Votive v3 has been released!
I have tried to install votive3.msi but I get an error:
"To install Votive, you need to first install ProjectAggregator2.msi,
which is available at http://wix.sourceforge.net.";
But, I ca
, I couldn't create a new project in
Visual Studio. In the New Project dialog, under Wix, the project template
list is empty. Is there some way to manually add the templates so I can
get started using the latest build?
thanks
Paul
On 9/16/06, Justin Rockwood
<[EMAIL PROTECTED
The good news is that you're not a complete n00b. :) Votive v2 does not have
support for passing in command line parameters to candle/light. However, all
you have to do is add the .wxl file to the project and then it should
automatically pass in the -loc parameter.
I would recommend that you insta
Well,
after many weeks of work, I've finally checked in Votive v3. It is now
available after any build >= 3.0.2115.0. You can download it from http://wix.sourceforge.net/releases/3.0.2115.0/Votive3.msi.
For details about what is in the new version, you can find
out on my blog. It also h
Did you use votive.msi or votive3.msi? The votive3.msi has a brand new
Votive that you'll probably want to use if you do use Votive. It's got all
sorts of new stuff and a lot of bug fixes. I think you'll find that it's
much more usable than votive2.
Justin
-Original Message-
From: [EMAIL
Yes, they should be installed with Votive but they're currently not. Bob has
been working on a fix for that, but it's not in yet.
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Friday, August 04, 2006 2:25 PM
To: 'david adams'
There are undoubtedly bugs in the Votive 2003, since I haven't done any
active work on it. All of my time has been spent on the new Votive release
that is coming very soon. You can read about it here if you want more
information: http://blogs.msdn.com/jrock/archive/2006/07/18/670149.aspx.
Just to
Unfortunately, this isn't supported in Votive yet. I've got it in the works,
but it's not checked in yet. Stay tuned. :) For now you'll just have to use
the command line to build.
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gordon Watts
Sent: M
. :) Good luck with your
software!
Justin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Goldman
Sent: Friday, June 30, 2006 6:43 PM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX-users] customaction runs
Daniel, here are some things you may want to consider:
* How are you going to service the files that you unzip?
* How are you going to support uninstall?
* How are you going to support rollback during an install or uninstall?
I fully appreciate that different software packages may have different
Unfortunately, extensions aren’t supported in Votive right now,
so you’ll have to build via the command line.
Justin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek
Cicerone
Sent: Monday, June 26, 2006 4:00 AM
To: 'Harrborg Richard'; 'Bob Arnson'
Cc: wix-use
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Rockwood
Sent: Wednesday, June 14, 2006 1:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RFC: Moving Wix 3.0 to use the .NET Framework 2.0
There has been some talk on the core team about moving Wix
3.0 over to use the .NET
1 - 100 of 101 matches
Mail list logo
