VS Configurations etc for KSP1.3.1 BackPort (#145)

* Build: Add VS configs for KSP1.3.1

Added configs `Debug 1.3` and `Release 1.3` that have the KSP13 define and set output dir with the KSPBACKPORTDIR Env var.
Also added PostEvents for them to build the correct Zip.

* Build: Updated the zip build .bat file to use the correct shaders

* CONTRIBUTING.md: Added BackPort information

CONTRIBUTING.md

@@ -317,14 +317,22 @@ This section will guide you through setting up your development environment so t
 
 #### Unity
 For building and/or debugging KSP Kerbalism with Visual Studio or Unity Editor you will need to download and install the exact version of Unity Editor that was used to build the version of KSP you are working with.
-You can find out which Unity version your current KSP install is using by looking at the first line of `C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program/output_log.txt`. It should read something like this:
+For KSP1.4.x You can find out which Unity version your current KSP install is using by looking at the first line of `C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program/output_log.txt`. It should read something like this:
 
     Initialize engine version: 2017.1.3p1 (02d73f71d3bd)
 
 In this case, the Unity version for your KSP version is 2017.1.3p1.
 
+And for KSP1.3.1 you can find out which Unity version your current KSP install is using by looking at the first line of `KSP_Data/output_log.txt` (or `KSP_x64_Data/output_log.txt`). It should read something like this:
+
+    Initialize engine version: 5.4.0p4 (b15b5ae035b7)
+
+In this case, the Unity version for your KSP version is 5.4.0p4.
+
+
 The Unity Editor for **KSP v1.4.x** is **Unity v2017.1.3p1** and can be downloaded here: [UnityDownloadAssistant-2017.1.3p1.exe](https://beta.unity3d.com/download/02d73f71d3bd/UnityDownloadAssistant-2017.1.3p1.exe )
 
+The Unity Editor for **KSP v1.3.1** is **Unity v5.4.0.p4** and can be downloaded here: [UnityDownloadAssistant-5.4.0p4.exe](https://beta.unity3d.com/download/b15b5ae035b7/UnityDownloadAssistant-5.4.0p4.exe )
 #### Visual Studio
 
 It is recommended to use **Visual Studio 2017**. Any version should work (including the free *Community* version).
@@ -379,11 +387,12 @@ Now you can choose between the Development version (launch `KSP_x64_Dbg.exe`) an
 
 #### System Environment Variables
 
-To make your life a little easier, the Kerbalism Visual Studio Project respects an environment variable called `KSPDEVDIR`.
-If you set its value to the path of your KSP development install, the reference and debugging paths inside the project should be set automatically.
+To make your life a little easier, the Kerbalism Visual Studio Project respects two environment variables called `KSPDEVDIR` and `KSPBACKPORTDIR`
+If you set their values to the paths of the relevant versions of your KSP development installs, the reference and debugging paths inside the project should be set automatically. Obviously `KSPDEVDIR` should point to your KSP1.4.x install and `KSPBACKPORTDIR` to your KSP1.3.1 install. 
 If it is not set, your reference paths and the Debugging paths have to be set manually.
+Please note that you don't need to use both installs if you plan on making private builds but if you plan on making pull requests then it will be appreciated if you make sure your code works for both versions. You can also use the compiler directive `KSP13` in the source to switch relevant code specific to a KSP version.
 
-To set the variable, follow the instructions in this link, before starting a Visual Studio instance:
+To set the variables, follow the instructions in this link, before starting a Visual Studio instance:
 
 https://superuser.com/a/949577
 
@@ -399,7 +408,9 @@ If you set your `KSPDEVDIR` variable as mentioned [above](#system-environment-va
   - Change to the **Reference Paths** tab and select the `\KSP_x64_Data\Managed` subdirectory of your KSP dev install
   - Click "Add" to actually add the selected path
 
-To be able to quicklaunch KSP using F5 (or Ctrl-F5), you have to set which external program should start. This should already be set if you set your `KSPDEVDIR` environment variable. If not,
+ Also when switching between the 1.4.x and 1.3.1 configurations you will have to manually change the references directory to point to the correct versions due to the limitation of VS not having the ability to switch reference directories via the configuration menu. (Thanks MS >.<) 
+
+ To be able to quicklaunch KSP using F5 (or Ctrl-F5), you have to set which external program should start. This should already be set if you set your `KSPDEVDIR` and/or `KSPBACKPORTDIR` environment variables. If not,
 
  - Double-Click the "Properties" page in the Solution Explorer in Visual Studio
  - Change to the **Debug** tab, select "Start External Program" and select the KSP executable that you want to start.
@@ -408,7 +419,9 @@ To be able to quicklaunch KSP using F5 (or Ctrl-F5), you have to set which exter
 #### Building
 
 If your reference paths are set up correctly, then building the project should be as simple as Clicking Build -> Build Solution.
-If `KSPDEVDIR` is set, then the output path will be the `\GameData\Kerbalism\` subdirectory of your KSP install. If not, you have to configure the output path yourself in Properties -> Build -> Output Path.
+If `KSPDEVDIR` and/or `KSPBACKPORTDIR` is set, then the output path will be the `\GameData\Kerbalism\` subdirectory of your KSP install. If not, you have to configure the output path yourself in Properties -> Build -> Output Path.
+
+You can use the configuration menu to switch between `Debug` and `Release` for KSP1.4.x and also `Debug 1.3` and `Release 1.3` for KSP1.3.1 , note you will have to manually set the references directory as mentioned [above](#development-and-debugging) when switching between KSP versions.
 
 When you are building in Debug mode, one additional file with the ending `.mdb` is created. This file is required for unity debugging.
 
@@ -497,8 +510,6 @@ To get a working development environment on mac, things are a little different.
 I didn't try to run KSP in a debugger yet. If you know how to do this, please update this guide. It might work with using the Launcher.app in your KSP folder (which is already used to build Kerbalism), so maybe you won't even have to download Unity.
 
 
-
-
 ## Building Releases
 
 Making releases is as simple as updating two version files and the clicking build. Below is a small checklist for releases.

Kerbalism.sln

@@ -7,12 +7,18 @@ Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Kerbalism", "src\Kerbalism.
 EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution
+		Debug 1.3|Any CPU = Debug 1.3|Any CPU
 		Debug|Any CPU = Debug|Any CPU
+		Release 1.3|Any CPU = Release 1.3|Any CPU
 		Release|Any CPU = Release|Any CPU
 	EndGlobalSection
 	GlobalSection(ProjectConfigurationPlatforms) = postSolution
+		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Debug 1.3|Any CPU.ActiveCfg = Debug 1.3|Any CPU
+		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Debug 1.3|Any CPU.Build.0 = Debug 1.3|Any CPU
 		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
 		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Release 1.3|Any CPU.ActiveCfg = Release 1.3|Any CPU
+		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Release 1.3|Any CPU.Build.0 = Release 1.3|Any CPU
 		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Release|Any CPU.ActiveCfg = Release|Any CPU
 		{7CF587A9-6E49-46E8-AB3F-87B80A6276DA}.Release|Any CPU.Build.0 = Release|Any CPU
 	EndGlobalSection

buildscripts/ZipPack/build-package.bat

@@ -8,6 +8,9 @@ rem get parameters that are passed by visual studio post build event
 SET TargetName=%1
 SET Dllversion=%~n2
 SET KSPversion=%3
+SET Shaders=%~n3
+SET Shaders=%Shaders:*KSP=%
+
 
 rem make sure the initial working directory is the one containing the current script
 SET scriptPath=%~dp0
@@ -31,10 +34,15 @@ xcopy /y /e "..\..\..\GameData\%TargetName%\*" .
 xcopy /y ..\..\..\CHANGELOG.md .
 xcopy /y ..\..\..\License .
 
+IF EXIST Shaders\ rd /s /q Shaders
+mkdir Shaders
+cd Shaders
+xcopy /y /e "..\..\..\..\buildscripts\Shaders\%Shaders%\*" .
+
 echo.
 echo Compressing %TargetName% for %KSPversion% Release Package...
 IF EXIST "%rootPath%%TargetName%*_For_%KSPversion%.zip" del "%rootPath%%TargetName%*_For_%KSPversion%.zip"
-"%scriptPath%7za.exe" a "..\..\..\%TargetName%%Dllversion%_For_%KSPversion%.zip" ..\..\GameData
+"%scriptPath%7za.exe" a "..\..\..\..\%TargetName%%Dllversion%_For_%KSPversion%.zip" ..\..\..\GameData
 
 cd "%rootPath%"
 rd /s /q package

src/Kerbalism.csproj

@@ -73,6 +73,32 @@
     <NoWarn>IDE0018</NoWarn>
     <LangVersion>latest</LangVersion>
   </PropertyGroup>
+  <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug 1.3|AnyCPU'">
+    <DebugSymbols>true</DebugSymbols>
+    <OutputPath Condition="Exists('$(KSPBACKPORTDIR)\GameData\Kerbalism\')">$(KSPBACKPORTDIR)\GameData\Kerbalism\</OutputPath>
+    <OutputPath Condition="!Exists('$(KSPBACKPORTDIR)\GameData\Kerbalism\')">obj\Kerbalism\</OutputPath>
+    <DefineConstants>TRACE;DEBUG;KSP13;DEVELOPMENT;ENABLE_PROFILER;DEBUG_PROFILER</DefineConstants>
+    <NoWarn>IDE0018</NoWarn>
+    <DebugType>full</DebugType>
+    <PlatformTarget>AnyCPU</PlatformTarget>
+    <LangVersion>latest</LangVersion>
+    <ErrorReport>prompt</ErrorReport>
+    <CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet>
+    <GenerateSerializationAssemblies>Auto</GenerateSerializationAssemblies>
+    <WarningLevel>3</WarningLevel>
+  </PropertyGroup>
+  <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release 1.3|AnyCPU'">
+    <OutputPath Condition="Exists('$(KSPBACKPORTDIR)\GameData\Kerbalism\')">$(KSPBACKPORTDIR)\GameData\Kerbalism\</OutputPath>
+    <OutputPath Condition="!Exists('$(KSPBACKPORTDIR)\GameData\Kerbalism\')">obj\Kerbalism\</OutputPath>
+    <Optimize>true</Optimize>
+    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
+    <NoWarn>IDE0018</NoWarn>
+    <PlatformTarget>AnyCPU</PlatformTarget>
+    <LangVersion>latest</LangVersion>
+    <CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet>
+    <DefineConstants>KSP13</DefineConstants>
+    <GenerateSerializationAssemblies>Auto</GenerateSerializationAssemblies>
+  </PropertyGroup>
   <ItemGroup>
     <Reference Include="Assembly-CSharp">
       <HintPath Condition="Exists('$(KSPDEVDIR)\KSP_x64_Data\Managed\Assembly-CSharp.dll')">$(KSPDEVDIR)\KSP_x64_Data\Managed\Assembly-CSharp.dll</HintPath>
@@ -270,6 +296,12 @@
   </PostBuildEventDependsOn>
     <PostBuildEvent Condition="'$(OS)' == 'Windows_NT'">if $(ConfigurationName)==Debug (call "$(ProjectDir)..\buildscripts\UnityDebug\prepare-debug.bat" $(TargetName))
 if $(ConfigurationName)==Release (call "$(ProjectDir)..\buildscripts\ZipPack\build-package.bat" $(TargetName) -v@(VersionNumber) KSP1.4.4)</PostBuildEvent>
+  </PropertyGroup>
+  <PropertyGroup>
+    <PostBuildEvent>if "$(ConfigurationName)"=="Debug" (call "$(ProjectDir)..\buildscripts\UnityDebug\prepare-debug.bat" $(TargetName))
+if "$(ConfigurationName)"=="Release" (call "$(ProjectDir)..\buildscripts\ZipPack\build-package.bat" $(TargetName) -v@(VersionNumber) KSP1.4.4)
+if "$(ConfigurationName)"=="Debug 1.3" (call "$(ProjectDir)..\buildscripts\UnityDebug\prepare-debug.bat" $(TargetName))
+if "$(ConfigurationName)"=="Release 1.3" (call "$(ProjectDir)..\buildscripts\ZipPack\build-package.bat" $(TargetName) -v@(VersionNumber) KSP1.3.1)</PostBuildEvent>
   </PropertyGroup>
   <ProjectExtensions>
     <VisualStudio>