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 wix38 Note, if you plan on making changes and submitting them upstream, the process is different. You need to create a fork on codeplex and then clone it. -----Original Message----- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, September 30, 2013 10:10 AM To: wix-devs@lists.sourceforge.net Subject: [WiX-devs] [SPAM] Re: [SPAM] Re: [SPAM] Re: Interested in helping on 3.8 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 before I got it working I discovered that I could just go to wix.codeplex.com, select the version of Wix source that I wanted and click download to get the source. But I know I still have to figure out git at some point in the future. 2) One of the issues in my 'VS2013 to build Wix 3.8' testing is that the VS2013 install did not include the VS shell, so when using the standard shell there some errors related to cl.exe is missing dependencies on mspdb100.dll. I had noticed at work similar errors when I did not use the VS2010 shell. So after Internet research I found that VS2010 shell runs a bat which adds the path to this dependency to %PATH%, which was the same step that I needed to do to get my VS2013 build to work in this regard. 3) I created build.cmd and buildInitialization.cmd scripts to make it easier to launch my various build tests and create logs as I work on debugging different build issues. The buildInitialization.cmd script has code that only calls the msbuild OneTimeWixBuildInitialization.proj if the user is an elevated user, and if not reports that the script failed because elevated privileges are needed. There is more work needed to make these scripts work at any path, but maybe at some point we could help users in this manner. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SPAM-Re-SPAM-Re-Interested-in-helping-on-3-8-tp7589298p7589303.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
