VS loves to screw around with the csproj format, so move all the custom rules
into separate files that it can't screw around with.
This also gives the added benefit of shutting up the warning about duplicate
AssemblyVersionInformation types, because apparently VS doesn't show files
that are included for compilation from external targets files but it still
includes them in the compilation (bug? feature? shrug)
Add instructions for the GitHub.Unity.OctokitDebugging solution
Add mono-built versions of octokit and dotnet-http.
Octokit: 0.23.0.1
dotnet-httpClient35: 3.5.0.0 (3.5.22000.1-gfu)
The root solution loads the projects inside the src folder and subfolders, and
the GitHub.Unity project puts its output DLLS in the unity\TestProject folder,
which serves as a Unity test project for the compiled DLLs. If we need to debug
the code in Unity, the src\UnityExtension folder is also a Unity project, and
Unity compiles the sources files in it, so everything should magically work.
ignore rules for Unity and non-Unity projects are mutually exclusive
(csproj files being ignored, DLLs allowed, .meta files being included in
Unity projects), so we need to keep the Unity projects in a separate tree from
the rest of the .net projects in order to easily have gitignore rules that work
for both
Andreia Gaita
Andreia Gaita
Stanley Goldman
Emil "AngryAnt" Johansen