This guide is for developers who want to set up a new solution that uses Quino.
- A solution should stick to a standard for its output folders
- The .NET compiler is faster when projects share a single output folder
- Quino uses a common output folder called
- Web applications that run in IIS Express must be run from a
A standard, non-web solution for Quino looks like this:
📁 src/ 📁 apps/ 📁 App.Console/ 📁 libs/ 📁 App.Core/ 📁 tests/ 📁 App.Tests/ 📁 out/
However, if a solution just uses the standard output folders, then the solution looks like this:
📁 src/ 📁 apps/ 📁 App.Web/ 📁 bin/ 📁 libs/ 📁 App.Core/ 📁 bin/ 📁 tests/ 📁 App.Tests/ 📁 bin/
An application will occasionally want to locate itself relative to where it's been compiled. This is different from the location from where it's running.
Therefore, Quino needs to know about the structure of the solution.
The main use case is when running tests, where the test runner often copies the assemblies to a remote folder. However, it's not very convenient to have to include all the data on which tests rely into the project and to mark it as "copy to output folder".
What kind of files are these?
- Configuration files
- Input for data generators (e.g. *.csv)
- Test inputs
- Expectation files
Quino applications use the Assembly Settings to get back to the source folder where the assembly was compiled. Together with the Project Settings, the application can then locate other folders in the solution.