Go to file
Pranav K 84c2e7cffe Do not attempt to add the designer file as part of the tt generation
This results in multiple copies of the .Designer file being added to the
project in different locations which gets confusing.
2014-03-03 12:10:57 -08:00
build Do not attempt to add the designer file as part of the tt generation 2014-03-03 12:10:57 -08:00
build-template Update the build template 2014-02-07 23:22:43 -08:00
.gitattributes
.gitignore
KoreBuild.nuspec
README.md Adding underscore to README 2014-02-06 11:00:29 -08:00
build.cmd
makefile.shade Fix #14: Clone inner repositories using matching GitHub URLs 2014-02-24 14:55:35 -08:00

README.md

Universe

Getting started

git clone git@github.com:aspnet/Universe.git
cd Universe
build

The default build will clone all known repos as subfolders. The clone will be the dev branch.

If the build is run subsequently it will git pull the dev branch rather than clone. Note! This will cause a merge if you have local changes. We may tweak how this is done if it causes problems.

After folders are up to date, build.cmd compile is executed in each of the enlisted subfolders.

If there are errors the build will continue with the next repo.

The last output is a list of which repos succeeded or failed.

build targets

build pull will only clone or pull all repos.

build compile this is the default target, described above.

build install works like build compile, but will run build.cmd install in each subfolder. This means any nupkg produced by the repo are copied into the local .nuget folder to be picked up by subsequent repositories. The subfolders are built in dependency order.