Game Development Reference
In-Depth Information
Figure 9.6
List of Solution folders.
hasn't been copied across to the EngineTest solution; it's just a reference. All its
code stays in the same place. This makes it easier to work with several projects
using the engine library but without duplicating the code. The Engine code can
be edited from any solution and all the changes will be shared with all projects
using the library.
You may notice that the font for the EngineTest project is in bold. This is because
when you run the solution, the EngineTest project will be executed. A solution
might contain several projects that could generate executables, and the Solution
Explorer needs to know which project you want to run and debug. You can make
the Engine project the start-up project by right-clicking its name in the Solution
Explorer and choosing Set as Start Up Project. The Engine project's name will
now turn bold, and the EngineTest project name will turn non-bold. Running
the project will produce an error stating class libraries are not executable. Right-
click the TestEngine project and set that as the start-up project again so you can
once again run the solution. This functionality is useful if you also wanted to
develop a level editor or other tool for your game. It could be added to the
solution as an additional project that makes use of the engine and game project.
Engine and TestEngine exist in the same solution, but at the moment they do not
have access to each other. TestEngine needs to access the code in Engine, but
Engine should never need to know about the TestEngine project. In the Solution
 
Search WWH ::




Custom Search