diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index eba0eb161..65b50cbde 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -26,10 +26,12 @@ To help make improvements to this project, you can just clone this repository an Before jumping in, please review the solution architecture and instructions below to [get started](#solution-architecture). +Please follow the [Development Guide](https://github.com/HTBox/allReady/blob/master/docs/prerequisite_install_guide/prerequisite_install_guide.md) to setup your development environment and build the project for launch and testing. + As of this writing (week of 7/20/2015), we are focused on expanding and filling out our documentation, issues lists, milestones plan and supporting any issues that arise from community engagement with the codebase. Additionally, you willl find issues of all types (simple bugs, new feature & requirements and architectural updates) upon which you can contribute to the project. In the meantime, if you find any issues with the codebase or other content in our repository please log an issue and we will work with you to solve it. Thank you for considering supporting this open source project for humanitarian support. ## Solution architecture -See the [Solution Architecture Guide](https://github.com/HTBox/allReady/wiki/Solution-architecture) for all of the details on how allReady is built. +See the [Solution Architecture Guide](https://github.com/HTBox/allReady/wiki/Solution-architecture) for all of the details on how allReady is constructed, built, and tested. \ No newline at end of file diff --git a/README.md b/README.md index 39dc16fdc..9af95c5b1 100644 --- a/README.md +++ b/README.md @@ -43,6 +43,6 @@ To help make improvements to this project, you can just clone this repository an > **Important** Before jumping in, please review the [solution architecture](https://github.com/HTBox/allReady/wiki/Solution-architecture) and instructions below to [get started](https://github.com/HTBox/allReady/wiki/Solution-architecture#get-started-with-the-allready-solution). It contains critical information on how to configure the project to run locally and optionally deploy AllReady to Azure. -Also we have a guide on setting up git for open source projects like allReady that can help you get started making contributions. You can find the [guide in our docs folder](https://github.com/HTBox/allReady/blob/master/docs/git/gitprocess.md) and it also reference a number of blog posts written with additional information on contributing to projects like ours. +Also we have a [contribution guide](https://github.com/HTBox/allReady/blob/master/CONTRIBUTING.md) on setting up git for open source projects like allReady that can help you get started making contributions. You can find the [guide in our docs folder](https://github.com/HTBox/allReady/blob/master/docs/git/gitprocess.md) and it also reference a number of blog posts written with additional information on contributing to projects like ours. Thank you for considering supporting this open source project for humanitarian support. diff --git a/docs/prerequisite_install_guide/images/web-11-manual-restore.png b/docs/prerequisite_install_guide/images/web-11-manual-restore.png new file mode 100644 index 000000000..b1d042189 Binary files /dev/null and b/docs/prerequisite_install_guide/images/web-11-manual-restore.png differ diff --git a/docs/prerequisite_install_guide/prerequisite_install_guide.md b/docs/prerequisite_install_guide/prerequisite_install_guide.md index 71f7bada7..adbef56a9 100644 --- a/docs/prerequisite_install_guide/prerequisite_install_guide.md +++ b/docs/prerequisite_install_guide/prerequisite_install_guide.md @@ -468,6 +468,13 @@ It may take a few minutes to compile the solution the first time. If all has went well your solution compiled successfully and you are ready to run the web site. +**Trouble Shooting** +Sometimes the package dependencies will not be automatically restored by the Visual Studio at your first build attempt, and this could trigger the build process to fail with lots of error messages, basically claiming that certain dependent files could not be located. If you have run into this issue, you will need to manually restore the dependency packages. + +To do this, go to Visual Studio's `Solution Explore`, expand the `Web` folder under the solution, then click the small triangle by the `Dependencies` to pen the dependency items tree, locate the `npm` entry, right click the entry, and click the `Restore Packages` from the context menu. This will launch the packages restoration process. After the status bar denote that the installations are complete, you can now build the solution again. + + ![Manually Restore the Dependency Packages](image/web-11-manual-restore.png) + ### Running The Web Site By default the Web project is set as the Startup Project. You can verify this in Solution Explorer by looking at the Web\AllReady project and seeing that it is bolded.