The DevBundle branch doesn’t have any of the tools that crashed for you. There’s no build directory created in the DevBundle branch either. It has an SLN file you can load into Visual Studio (if you have WiX installed already) or build using MSBuild (also requires WiX available) that contains just one WIXPROJ. Are you really sure you are actually in the DevBundle branch?
Simple way out: under src\packages, just open each folder and install what you find there. -Blair From: Smagin Alexander Sent: Tuesday, December 03, 2013 8:08 AM To: General discussion for Windows Installer XML toolset. Blair, thank you for slarification. But when I start building DevBundle, GenerateWixInclude.exe and docfromxsd.exe have crashed. There are exceptions which generated during building. Do you know how to fix them? Sorry for russian error messages, I can translate if it's necessary. "d:\Install\Wix\DevBundle\build\debug\x86\GenerateWixInclude.exe" -nologo "custommsierrors.h" "d:\Install\Wix\DevBundle\build\d ebug\inc\caerr.wxi" Необработанное исключение: System.IO.FileLoadException: Невозможно загрузить файл или сборку "GenerateWixInclude, Version=3.0.0 .0, Culture=neutral, PublicKeyToken=36e4ce08b8ecfb17" или один из зависимых от них компонентов. Сбой при проверке правильности строгого имени. (Исключение из HRESULT: 0x8013141A) Имя файла: "GenerateWixInclude, Version=3.0.0.0, Culture=neutral, PublicKeyToken=36e4ce08b8ecfb17" ---> System.Security.Securit yException: Сбой при проверке правильности строгого имени. (Исключение из HRESULT: 0x8013141A) Ошибкой завершилась сборка со следующим параметром Zone: MyComputer "d:\Install\Wix\DevBundle\build\debug\x86\docfromxsd.exe" -out "d:\Install\Wix\DevBundle\build\obj\debug\x86\chm\documents\xsd" "..\libs\dutil\xsd\thmutil.xsd" "..\tools\wix\Xsd\wix.xsd" "..\tools\wix\Xsd\wixloc.xsd" "..\ext\BalExtension\wixext\Xsd\bal.x sd" "..\ext\ComPlusExtension\wixext\xsd\complus.xsd" "..\ext\DependencyExtension\wixext\Xsd\Dependency.xsd" "..\ext\DifxAppExte nsion\wixext\Xsd\difxapp.xsd" "..\ext\FirewallExtension\wixext\Xsd\firewall.xsd" "..\ext\GamingExtension\wixext\Xsd\gaming.xsd" "..\ext\IIsExtension\wixext\xsd\iis.xsd" "..\ext\MsmqExtension\wixext\xsd\msmq.xsd" "..\ext\NetFxExtension\wixext\Xsd\netfx.xs d" "..\ext\PSExtension\wixext\xsd\ps.xsd" "..\ext\SqlExtension\wixext\Xsd\sql.xsd" "..\ext\TagExtension\wixext\Xsd\tag.xsd" ".. \ext\UtilExtension\wixext\Xsd\util.xsd" "..\ext\VSExtension\wixext\xsd\vs.xsd" "..\ext\lux\wixext\Xsd\lux.xsd" Необработанное исключение: System.IO.FileLoadException: Невозможно загрузить файл или сборку "DocFromXsd, Version=3.0.0.0, Cult ure=neutral, PublicKeyToken=36e4ce08b8ecfb17" или один из зависимых от них компонентов. Сбой при проверке правильности строгого имени. (Исключение из HRESULT: 0x8013141A) Имя файла: "DocFromXsd, Version=3.0.0.0, Culture=neutral, PublicKeyToken=36e4ce08b8ecfb17" ---> System.Security.SecurityExcepti on: Сбой при проверке правильности строгого имени. (Исключение из HRESULT: 0x8013141A) Ошибкой завершилась сборка со следующим параметром Zone: MyComputer Thanks, Alex. Вторник, 3 декабря 2013, 15:13 UTC от Blair Murri <os...@live.com>: >You will need to first install .Net Framework 3.5, recent versions of Visual >Studio (2010 or newer), then build and install the DevBundle branch (you can >remove the DevBundle installer if you wish, all the components it installs are >marked "permanent"). If you install multiple versions of VS, it is recommended >to install them in chronological order (personal experience) with their latest >service packs. > >Build instructions are (more-or-less) described here (the prerequisites >described are most easily obtained by following my previous instructions): >http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html > >The biggest missing piece from the above documentation pages is that >tools\OneTimeWixBuildInitialization.proj must be built using MSBuild from an >elevated command prompt at least once on any given build/dev box before you >can build the rest of the toolset (otherwise you will get build errors >starting early on). Also, it is best to build the entire toolset from the root >of the sources (after having built that one project file elevated) before you >descend into sub directories to work/build individual portions. Running the >developer command prompts for Visual Studio usually isn't necessary, although >MSBuild isn't usually in the path. You'll need the v4 MSBuild, which you can >add your path yourself, use the developer command prompt, prepend the MSBuild >calls with the path to the tool, or create your own alias/batch file to call >the tool. > >-Blair > >From: Smagin Alexander >Sent: Tuesday, December 03, 2013 6:31 AM >To: General discussion for Windows Installer XML toolset. > >Hi people, >I want to compile wix from source code, but I didn't find any readme files >"how to comlipe wix". > >Could any one give suggestions which tools are used and where I can read anout >it? > >Thanks, >Alex. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
