Skip to content

Latest commit

 

History

History
47 lines (28 loc) · 2.26 KB

TerminalDeveloping-GettingStarted.md

File metadata and controls

47 lines (28 loc) · 2.26 KB
Raw

Building a .Net Terminal - Getting Started

.NET SDK Home

.NET Terminal Developer Guide Home

Step 1: Install Required software

  1. Visual Studio 2015 is required. The Community Edition is known to work at the time of this writing.
  2. Node.js See notes below
  3. TypeScript 1.8 (automatically installed by recent versions of Visual Studio)
  4. .NET 4.5 is required. In addition, .NET 3.5 must also be enabled in your environment. Instructions are here.
  5. Git
  6. Azure SDK 2.7.#

Installing Node

Getting Node to work with Visual Studio has proven to be tricky. Simply installing Node onto your computer isn't usually sufficient. The test is this: if you can go to the Package Manager Console and type npm, then Visual Studio can see your local node installation. If it can't, the key seems to be to manually add a path to your node installation to your system PATH.

In this image you can see the useless "Roaming" path that seems to get added automatically by node installation, but which doesn't seem to work (at least for Visual Studio). The developer here has done an install of Node and explicitly installed it into c:/code/npm, and then added that path. This seems to be sufficient to get Visual Studio to see npm.

Step 2: Install a Local Development Database

If you are planning to run Hub locally you'll need to configure a sql database. Otherwise, you can skip this step. Fr8 uses EntityFramework 6.1 to interact with data. Fr8 uses CodeFirst Migrations.

Step 3: Clone the Repositories

Start by cloning Fr8Core. This will provide you with all Hub and Client code, and all of the Terminals that have been written in .NET.

Step 4: Build and Run Fr8

Build and Run

Next: Try building a Terminal Project