Do-it-yourself Bible audio recording
C# TeX Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.nuget
DistFiles
artwork
build
design
lib/dotnet
packages
src
.editorconfig
.gitattributes
.gitignore
Copy Libaries.bat
Copy ParatextShared Debug Libaries.bat
Copy ParatextShared Release Libaries from Paratext 8.bat
Copy ParatextShared locally built Release Libaries.bat
HearThis.sln
LICENSE.txt
ReadMe.md

ReadMe.md

Users

You're in the wrong place. Head over to http://software.sil.org/hearthis .

Testers

Please see Tips for Testing Palaso Software

Developers

Getting dependencies

  1. Ensure you have something that can run bash scripts
  2. Run build/get-dependencies-windows.sh
  3. Ensure you have Nuget installed
  4. Building the solution should automatically pull down the nuget dependencies.
  5. Assemblies not available on the build server or via nuget are checked in to the repo in lib/dotnet. When working on the code, the development team needs to decide if any of these assemblies should be replaced with the latest version.

RoadMap / Day-to-day progress

See the HearThis Trello Board

Continuous Build System

Each time code is checked in, an automatic build begins on our TeamCity build server, running all the unit tests. Similarly, when there is a new version of some HearThis dependency (e.g. LibPalaso, LocalizationManager), that server automatically rebuilds HearThis. This automatic build doesn't publish a new installer, however. That kind of build is launched manually, by pressing a button on the TeamCity page. This "publish" process builds HearThis, makes and installer, rsyncs it to the distribution server, and writes out a a json file that the downloads page reads so that it can display options to the user.

Coding Standards

Please avoid making spurious white space changes. HearThis uses tabs, not spaces, for indentation.