Installation Instructions
Please follow the steps below carefully. If you encounter any problems, please check the
FAQ.
There are no binaries included in the ZIP file. You will need Visual Studio 2010 C# (Express Edition or higher) to compile the samples. Make sure that you have Visual Studio and RDS installed before you try to install these samples.
- Download the ZIP file from the Downloads page.
- Unzip the file into a folder called ProMRDS under your RDS installation folder (which should be something like C:\Users\xxxx\Microsoft Robotics Developer Studio 4 Beta). Do not unzip the files somewhere else on your hard drive because the code might not compile correctly. Note that the ZIP file contains the ProMRDS folder, so be careful not to create it twice.
- Open a DSS Command Prompt. (Look in the Start Menu under Microsoft Robotics Developer Studio).
- When the console window appears, type in the following commands:
cd ProMRDS
setup.cmd
NOTE: The setup.cmd should run DssProjectMigration to fix up the paths in all of the project files. If you cannot compile and you see references to non-existent folders like C:\Users\xxxx\... then DssProjectMigration has not run properly. Please try running it manually on the whole of the ProMRDS folder.
If you have a robot from Robotics Connection (see Chapter 16) then you might also want to download the Robotics Connection services from this web site. These need to be unzipped into the Samples\Platforms folder and then compiled before you try to build Chapter 16.
Building the SamplesThe source code is now set up and you should be able to open any of the Solutions in Visual Studio and compile them. However, the services in some Chapters depend on other Chapters so it is advisable to compile all of the code samples.
- Compile all of the code by entering the following command at the DSS Command Prompt:
buildall.cmd
NOTE: Due to dependencies it might be necessary to run buildall.cmd twice.
Each of the Chapter folders contains a script called
buildall.cmd that can be used to recompile the samples in that Chapter. The top-level
buildall.cmd simply calls the buildall scripts in each Chapter.
There is also a script called
clean.cmd that can be used to delete all of the files produced during compilation to clean up the source tree. This script does
not delete the service DLLs from the
bin folder however.
Checking the InstallationTest the installation by entering the following command at the DSS Command Prompt:
Welcome
This should run a simple "Hello World" type of service from Chapter 1.
You can also test the simulation by entering the command:
Teleoperation
This will run the Maze Simulator with the TeleOperation service so that you can drive the simulated robot around.
Getting More InformationThere is are HTML web pages included with the source. The top page is called
ReadMe.htm. Open this page in a web browser to find out more about the contents of each Chapter.