huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
39 Commits 1 Branch 0 Tags 251 MiB
C# 84.1%
JavaScript 7.1%
C++ 2.9%
HTML 2.5%
TypeScript 1.3%
Other 1.9%
Go to file
David Fowler 1964e884e1 Initial version of watch target. 
- Added FileWatcher helper class
- Added ability to disable fetching k from nuget every time it's called
- Added watch target to standard goals
- Added ability to skip project generation for net45.
  This is useful for watch so that changes made to the
  project but not saved to disk won't be discarded when the
  watcher runs.
 		2014-02-01 11:55:10 -08:00
build Initial version of watch target. 2014-02-01 11:55:10 -08:00
build-template Added template files and updated the init task. 2014-01-28 22:50:42 -08:00
.gitattributes Added template files and updated the init task. 2014-01-28 22:50:42 -08:00
.gitignore
…
KoreBuild.nuspec Changed package name to KoreBuild. 2014-01-25 01:12:12 -08:00
README.md Update README.md 2014-01-23 20:24:47 -08:00
build.cmd Updated build file to makefile.shade 2014-01-23 22:31:19 -08:00
makefile.shade Added template files and updated the init task. 2014-01-28 22:50:42 -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.