This project is read-only.
Setting up a Development Environment

CIPl builds serializers for the CIP4.Browser and several of the tests as a part of the normal build process. The CIP4.CMD app is found using the environment variable CIP4_HOME. This must point to the directory containing the CIP4 binaries directory. The CIP4 tests use a CIP4 provided collection for holding expected test results. This collection must be available before you can run any tests, as virtually all of them make use of it. The CIP4_HOME environment variable is set by the CIP4.Setup, so if you point CIP4_HOME to a development location you will have to point it back again if you happen to run setup.

Bearing all that in mind, development setup instructions are as follows:

1. If you're a developer do the usual Visual Studio/TFS thing to get the source files - if you just want to get and build the source files pick a Change Set and download the zip file containing the sources
2. Set CIP4_HOME to point to wherever you put the CIP4.sln file
2. Build the CIP4.Installer project - this should build CMD, Core, RulesEngine, Serializer and Simple. It should also create a Binaries directory in your development environment
3. Go to the TestDataManager project in the solution's Test directory and open the Setup.bat file
4. Follow the instructions in the .bat file - you must do steps 1-3, do whichever of 4 you're interested in
5. Build the CIP4.sln
6. Run the tests

If you download and unzip the CIPl files, all the executable files in the Third Party directory will be marked as blocked. You can unblock them by installing the sysinternals suite (at least streams.exe) and do the following in the CIP4 directory, targeting the Third Party directory before you do a compile:

>streams.exe -d -s "Third Party"

If you make any changes to CIP4 it is strongly recommended that you run the CIP4.MultiThread application and test cross thread and especially cross process scenarios.

Last edited Oct 26, 2010 at 3:56 PM by PatrickThompson, version 6


No comments yet.