To clarify what's involved (or what might be involved) in getting Votive
support for VS2013:
http://www.joyofsetup.com/2013/09/30/wix-v3-8-todo-list-votive-2013/
--
sig://boB
http://joyofsetup.com/
--
October Webinars:
Git is distributed; the repositories are all completely independent copies. As
such, you can work on multiple features locally each in their own feature
branch and then push all or one of the feature branches in question to your
fork on codeplex.
My personal strategy is to locally tie my reposi
I created a fork on codeplex and made the seemingly incorrect assumption
that I was essentially creating a fork off the 38 branch. In fact I was
forking everything and still had to do the git checkout wix38 (using
Tortoise Git though ).
Using other tools such as Clearcase and TFS I'm used to
As far as git goes, I'd start with http://git-scm.com/book/en/Getting-Started
The short version is after you've installed git, you should be able to:
1) Open your git bash
2) Navigate to where you would like the git source to go
3) git clone https://git01.codeplex.com/wix
4) cd wix
5) git checkout
Regarding Christophers' last #5 post, I have seen the same issues, both in
regard to the error on a Win 7 32 which does not have a PF (x86) and on Win
8 64 (which I am currently trying to resolve). The docs and msdn are
confusing and I could not install the downloaded setup. I just completed
unin
Rob suggested:
>>If you're just getting started, a really easy bug to fix might be good
place to start. #4037 (http://wixtoolset.org/issues/4037/) might be a good
one.
I read #4037 bug and checked the link in the document on the websit
(http://wixtoolset.org/documentation/manual/v3/xsd/wix/customa
I just remembered #5. The help doco says that the HTML Help SDK can be if
C:\Program Files or C:\Program Files (X86). I don't think this is entirely
true. I followed the links to the MSFT website and there was a lot of
branding confusion over what version I was downloading. Some screens said
Thanks. I will look at that. At home on my 'new' Win 7 x86 box, I have been
working for almost three weeks to get Wix 3.8 to build on VS2013. I tracked
down and resolved a number of lot of issues. Some relate to PC
configuration and others required changes to targets and .props files.
However
I would just like to inject a couple of comments to this thread, based on my
current research into using VS2013 to build the Wix 3.8 source.
1) I do not have any prior experience with git and still have not figured it
out. I started working on it several weeks ago to get the Wix 3.8 source
and be
On 9/30/2013 4:20 PM, Christopher Painter wrote:
I've used a number of SCC tools over the year and have only used Git
in the past month. It was GitHub though and a totally different
experience. I stumbled with Codeplex UI. They show you the source
with a dropdown of branches and a download b
Rob,
I've created an account on wixtoolset.org and logged in. Every time I try
to save a comment I get:
Error! Something went awry while submitting your changes. Please, try
again.
I've tried with IE and Chrome. My comment for #4037 was going to be:
Tested with wix3.7 and wix3.8. I can
I've used a number of SCC tools over the year and have only used Git in the
past month. It was GitHub though and a totally different experience. I
stumbled with Codeplex UI. They show you the source with a dropdown of
branches and a download button and you kind of expect that if I select wix
At $work we mostly use Mercurial (previous jobs used CVS and ClearCase) and
colleagues struggled to learn git when they moved onto a new project. At a
minimum we probably need to advise people to add “-b wix38” etc. when cloning
the repository.
--
Bruce
From: Rob Mensching [mailto:r...@robmen
1. Do we need to write a tutorial for git for WiX toolset? I'd hoped git
had taken over the world enough that we don't need a tutorial how to
download code with it. No?
2. I use an empty cmd shell most of the time. Things *should* just work but
if you have a permutation that you used that didn't w
Rob,
I agree it *is* much better then it used to be. Still, I did hit a number
of road bumps over the weekend. The problem is it's hard for me to write
up any suggestions because my conclusions could be all wrong. And it's
hard for you to identify the gaps due to you already knowing the ins
Your notes and any thoughts on getting the WiX toolset build process easier
would be very useful. We've done work over last few releases to get WiX
toolset much easier to build but if there is more we can do, we should do
it. People still say there are challenges building the WiX toolset.
If you'r
Underway.
On Fri, Sep 27, 2013 at 2:58 PM, Christopher Painter wrote:
> Requesting.
>
> Thanks,
> Chris
>
>
>
> --
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application perfor
17 matches
Mail list logo
