A collection of projects and notes you would expect to find on a .NET developer’s workstation.
At the very top of the trunk are PowerShell scripts. These compose and invoke the code (see below) present in the NoFuture solution.
A directory containing notes from technical text and a handful of cook-book style code snippets which are prefixed with an underscore.
This directory contains all the related code and forms the majority of the content. The code is from various languages but the vast majority is C#. In all, the following languages are present:
- C#
- F#
- JavaScript
- Java
- R
- Python
- C++
The following is a logical grouping of code projects found herein. Any project with .Core in its namespace is a splinter assembly which was separated from its parent to allow for compilation in .NET Core. Furthermore, if a project has a Python equivalent then it will be likenamed with a _ py suffix. Projects named with .Invoke[...] are typically console apps which were isolated from their parent namespace for dependency reasons - they will either send data back on the standard output or on a socket.
An assembly for types which are shared by other assemblies which do not themselves have any reference to each other.
This is your typical common assembly which defines the types, paths, keys, strings, etc. which are environment-wide. They are defined in a custom configuration file named nfConfig.cfg.xml. A custom configuration file is used to allow for the same data to be used by the counterpart Python project shared_py and to avoid a dependency on the .NET System.Configuration namespace.
This is your typical toolbox assembly which defines those common string, path, net, math, etc. operations that developers use.
A collection of projects for parsing structured data.
This is a modified copy of the like-named project from Microsoft. See its README.md for more information.
This is a my encryption library dealing in X509 certs and client-side JavaScript encryption.
This is an assembly which I use for modifying MsBuild project files .NET configuration files, Visual Studio solution files, NuGet package files and INI files.
This is my tool box for various SQL queries (currently only MSSQL).
This is a pair of assemblies which allow for hosting an ASP.NET web app without using IIS.
This is a set of assemblies geared for code generation and removal. This has a dependencies on Dia2Dump and NoFuture.Antlr mentioned above.
This is a whole set of tools for generating ORM entities.
This contains projects which are executable hosts of other projects in NoFuture.
This is a collection projects for generating test data at random (see the README.md in its directory for more).
This project is both an API for generating timeline diagrams (in text format) and an implementation of timelines for the history of Western Civilization (3000 BCE - 1992 CE).
The actual code is decorated with a lot of annotations, comments and examples. Any external sources are cited in the function's annotation. The tests in NoFuture.Tests are dependent on files on the drive and would take some tinkering to get running green. This was due to the odd nature of what some of the code does (like getting a method's MetadataToken off a .NET assembly by reading the IL bytes). The kind of main() for the whole thing is the start.ps1 PowerShell script. Its intended to basically setup the PowerShell console (prefer the ISE) with the contents of the entire namespace.
This project was originally hosted with Google Code as an SVN repo. After Google stopped support I moved it to a Git repo in GitHub. Its overall structure still displays remenants of its SVN roots.