From a personal point-of-view, I like to keep "plumbing code" and "business logic" separate. The most common approach I take to do this is create various library projects and reference them in the main project. This all happens in the same solution if I can help it. Because of this preference, I designed Console.Waterworks (C.W.) to operate with this as the default context.
Because this repository does not utilise this set-up, I will provide you with a link to another project which does. It is called Wet Pancake and the links for its repository and wiki are as follows:
Within Wet Pancake is a .Net Standard Library (written in F#) and a .Net 4.7 console project (written in C#). The console project uses Console.Waterworks (C.W.) and references the F# library (yes, two different languages). I am hoping this is convincing enough for you.
For the sake of completeness, here is a quick overview of Wet Pancakes' set-up.
In more generic terms, here are a couple of diagrams to help explain where/how C.W. slots into your project.
An important note to make is your must call the code from another library inside the command-methods.
If you are unsure how to reference a .Net library in another project, within your solution, use the following link for more information:
Table of Contents
As Source Code
Console.Waterworks
- Console.Waterworks Home
- Console.Waterworks Project Breakdown
- Console.Waterworks Flow
- Coercion Types List
- The Help Attributes