Building

Developer Build

You need:

• Source of this repository
• Source of dotnet-packages
• Visual Studio Community 2017
• Microsoft Build Tools 2013 (v12)
• Microsoft Build Tools 2015 (v14)
• Cygwin (with additional packages: unzip, patch)

You should:

• Add C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin to PATH-Variable (buildscripts need to use MSBuild.exe from this path)
• Add C:\Program Files (x86)\Windows Kits\<VERSION>\bin\<ARCH> to PATH-Variable (buildscripts need to use rc.exe and others from this path)

Build dotnet-packages (3rd Party Libraries)

1.) Open cygwin-Konsole and change to root folder of repo

cd <path-to-dotnet-packages>

3.) Build it

./build.sh

4.) The libraries should now be in _build\output

Build

1.) Copy content of dotnet-packages\_build\output\dotnet46 to <path-to-repo>\packages

2.) (optional branding) Open cygwin-Konsole, execute

BUILD_NUMBER=1 <path-to-repo>/branding-xcp-ng/brand-to-xcp-ng.sh

2.) Open XenAdmin.sln

3.) Build and enjoy

Run Tests (not released version 7.4.2+)

You need:

• Nunit 3 Testadapter (Visual Studio Plugin)

1.) compile complete solution

2.) go to test explorer window

3.) run tests :-)

---

The information presented below may be incorrect, so handle with care 👮‍♂️

Build with CI (Jenkins) [work in progress]

You need:

• Jenkins with some plugins: Pipline,...
• Buildnode (same environment as described in Developer Build)
• Jenkins Workspace path without spaces in pathname

Internal structure of original buildscript mk\build.sh

1. clean build folder
2. branding (Branding/branding.sh, mk/re-branding.sh) - sets version numbers, product name and company name from branding repo
3. build
4. WIX (https://de.wikipedia.org/wiki/Windows_Installer_XML)
5. build/sign installers (mk/build-installers.sh)
6. ...do some ressource and validators stuff...
7. prepare stuff for iso