With Visual Studio 2005, you can use the Milos Project Templates to create new solutions quickly. In VS 2003, you have to create new Milos solutions manually. In either case, EPS recommends a standard configuration described below.

Note: While the use of a standard configuration is not necessary for the Milos components to work, the EPS standard configuration reflects industry Best Practices and makes learning the Milos components and maintaining Milos applications easier.

The Milos Solution Platform is created in a number of individual solutions. Each solution focuses on a specific sub-domain of the platform. You are encouraged to follow this methodology with your solutions.

Solutions generally contain projects that are logically related. For instance, there is a solution that contains all the SQL Server specific components. Assemblies dealing with other databases such as MySQL are stored in different solutions. This helps keep individual solutions at manageable sizes. It also allows developers to work on individual components without having to have a development environment that supports all the needs of all the individual assemblies. For instance, a developer working on SQL Server components does not have to have MySQL components installed, since MySQL is handled in a different solution. If the MySQL projects were in the same solution as the SQL Server projects, then this developer could not recompile the SQL Server components without having MySQL libraries and the MySQL database engine installed.

• Solution Folder Structure
  
• Project Settings