Before digging too far into the project, it is a good idea to know why it exists. On top of that, you should, also, know about its limitation. Without either of these two pieces of information, you will likely find frustration; Which is no use to anyone.
Why This Repository Exists
I stumbled upon a project called ConsoleApplicationBase by TypeCast Exception. I liked it and it solved a problem I had at the time. After a while, I became frustrated with the set-up time needed with each new project. (This was more so with small/throwaway projects.) When my level of frustration crossed the tipping point, I decided to take the ConsoleApplicationBase template and package it up into NuGet. The aim was to create something which mimics what ConsoleApplicationBase does but with less set-up/ceremony. Console.Waterworks was the result.
You can find out more about TypeCast Exception's project by using the following links:
- TypeCast Exception's GitHub Profile
- ConsoleApplicationBase Reposoitory
- TypeCast Exception's Blog Post on ConsoleApplicationBase
Limitations of this Repository
The repository is strictly a traditional .Net one. Every project was written with .Net 4.7 and no .Net Core stuff will be used. With Microsoft pushing .Net Core more and more, this package's days might be short-lived. Please weigh-up this and the .Net Core version of this package carefully.
Please use the following links if you are interested in using Console.Waterworks.Core -- instead of this one:
The Reason for no Visual Basic Repository
The simple answer is I do not know Visual Basic. If you do know Visual Basic and would like to provide something like this repository, feel free to do so.
Table of Contents
As Source Code
Console.Waterworks
- Console.Waterworks Home
- Console.Waterworks Project Breakdown
- Console.Waterworks Flow
- Coercion Types List
- The Help Attributes