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 wix38 
it'll download wix38.  It does not.  Also they show you the clone command and 
you think it'll get you on 38 but it doesn't.   I did find a place where you 
can look at history and download the changeset and that does get you wix38.    
So this is going on at the same time I'm trying to figure out how to build the 
source that I finally realize that I wasn't always getting the source that I 
thought I was getting.  Oh and I went down a rabbit hole of setting up Mecurial 
based on Bob's old blog post when I didn't need to.

No, I don't expect a full tutorial  but certainly 3-5 tips would probably help 
a new guy like myself. :)

#2 - What is an empty cmd shell to you?  x86 or x64?  Which version of MSBuild 
in the path?  I don't expect all permutations to work, I just want to know 
which permutation would be ideal.

#3- Seems like it should be mentioned here: 
http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html     This 
seems to be /src/chm/documents/wixdev/building_wix.html.md  but I'm guessing 
the website doesn't get it from the wix38 branch.

#4- That was the issue. I finally thought I had a good build but in reality I 
had a votive.msi with 1 file it.  It just happened to be I was very interested 
in votive so the disappointment was more in realizing that I had a good build 
but not a good full build and that I still had more to figure out before I 
could start playing.

#5. Bummer agreed.  I'll reset the VM and discover them again no doubt. :)

----------------------------------------
 From: "Bruce Cran" <bc...@fusionio.com>
Sent: Monday, September 30, 2013 9:36 AM
To: "Windows Installer XML toolset developer mailing list" 
<wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] [SPAM] Re:  [SPAM] Re: Interested in helping on 3.8

  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...@robmensching.com]
Sent: Monday, September 30, 2013 3:27 PM
To: Christopher Painter; Windows Installer XML toolset developer mailing list
Subject: [WiX-devs] [SPAM] Re: [SPAM] Re: Interested in helping on 3.8    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 work we can try to 
get it fixed. To be clear, there are a *lot* of configurations that could be 
tested. It's non-trivial.       3. That'd be a great thing to contribute. Can 
you add it to the documentation where you thought it should have been spelled 
out?       4. That doesn't sound right. I have a machine with VS2008 and VS2010 
and it skips all VS2012 stuff. I now have a VS2012 machine and it skips all the 
VS2008 and VS2010 stuff. What issues did you have?       5. Bummer indeed.      
 That's how we got what we have today. There are a lot of permutations and I'm 
do not have the time to create the VMs to test them all. Instead, if one has a 
configuration that doesn't work, let's capture what we can from that and 
improve.       On Mon, Sep 30, 2013 at 7:13 AM, Christopher Painter 
<chr...@iswix.com> wrote: 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 and outs.   Make sense? 
    I think the process is pretty good as it stands now.... just  more 
documentation in the how to build wix needs to exist.   I had to scrape several 
sources  (some old and outdated)  to get to a point of building.  Some high 
level issues were:

1) Pulling source from CodePlex.  Bob's blog talked about Mecurial but now it 
seems to be Git. (Depending on what branch you are on?)
2) What version and bitness of vs command tools should be used?  (I was getting 
CreateItem task errors out of the nuget targets.)
3) It seems OneTimeWixBuildInitialization.proj has to be built as admin.  The 
help topic doesn't cover this.
4) It seems there are conditional compiles that are only enforced for an 
"official build".  Good design, but tough for a new guy that doesn't know this. 
 I had to turn to twitter to figure this out.
5) Others I sadly don't recall....

I guess my advice is start with a clean VM and pretend you don't know anything 
about WiX and see what's involved in getting it all to build.

Regards,
Chris
----------------------------------------
   From: "Rob Mensching" <r...@robmensching.com>
Sent: Monday, September 30, 2013 9:02 AM
To: "Windows Installer XML toolset developer mailing list" 
<wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] [SPAM] Re: Interested in helping on 3.8      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'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.       On Thu, Sep 26, 
2013 at 2:00 PM, Phill Hogland <phogl...@rimage.com> wrote: I am interested in 
offering any help I can provide.  I am relatively new to
wix, msi, msbuild, c# but I have too many years of doing pure InstallScript
setups and C++ services and drivers.  Please let me know how I can help
test, document, code, or whatever.

While waiting for my legal/management team to approve the assignment
agreement, approved and submitted to Outercurve this morning, in addition to
configuring my work development system to build the debug version of Wix
3.8, at home I created a new PC (Win 7 64, but I can load other OS),
installed VS2013, VS2013 SDK, Win 7 SDK, and the latest Wix 3.8 source code.
I have over the last several nights been trying to hack past problems with
building the full wix.proj, and keeping notes so I can report back if that
would be helpful.  It wants me to install Win7 SDK (which is installed) or
VS2010 (which is not installed).  So for now I am just trying to learn more
about the build process by researching these issues.  But I am happy to
refocus on anything that would be more helpful.

--
View this message in context:  
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Interested-in-helping-on-3-8-tp7589266.html
Sent from the wix-devs mailing list archive at Nabble.com.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs          
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

This e-mail (and any attachments) is confidential and may be privileged.  Any 
unauthorized use, copying, disclosure or dissemination of this communication is 
prohibited.  If you are not the intended recipient,  please notify the sender 
immediately and delete all copies of the message and its attachments.
  ­­

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to