The API for FlightNode is essentially structured along the lines of the onion architecture concept. Follow that link for a full description of the concept. Because my graphics toolkit is currently limited, my diagram for FlightNode has boxes instead of concentric onion-looking circles...
This release candidate nearly wraps up the user management and volunteer work tracking functionality. There are a small few "should have" features that will be added in a future release. So what's new?
Back in the '90s, I remember my parents saying that it was less expensive to inspect their cars in Plano, in Collin County, than a few miles further south in Dallas County - because of the additional emissions inspections required in the latter. I never would have imagined that 20 years later, ten DFW counties are now in non-attainment for smog-producing ozone pollution - and we still have no plan to solve the problem.
Just looking at the smog, we all know it can't be good for any of us. The American Lung Association has a good article on the health effects of ozone pollution. Moreover, studies have shown that air pollution in general has a disproportionate impact on Latino and African-American communities.
The .NET projects for FlightNode were created in several different Git repositories, thus giving us several small, well-contained, and re-usable projects. These small projects would be installed into the Service project as NuGet packages, which also makes for a faster compile in each discrete solution:
But… this has approach has caused problems.
The first beta release of FlightNode is now alive and in the hands of testers. So what's been delivered?
Wow, you'd think nothing had been happening for the past two months. But that's not the case at all. There are now 6 different GitHub repositories (perhaps a few too many). November and December were heads-down coding months. But now the product is almost ready for an MVP launch... and that has me thinking about error handling. Specifically, logging.
Originally I decided to look into NLog for .NET logging, a product I've never used before. I have experience with the Enterprise Library logging block and with Log4Net, and find them both to be useful but not as... pleasant... as I would like. They don't have the interface I would prefer. But they work. It turns out NLog has basically the same interface, and the same tedious configuration.
Twenty-something years ago, not long after the Exxon Valdez disaster, I wrote a research paper on solar power for my middle school Earth science class. I've been trying to lower my consumption, and looking forward to rooftop solar, ever since. The wait is finally over.
Well, almost. The panels are on the roof, but now I have 4-6 weeks to wait until the electric grid company (Oncor) comes out to inspect.
In order to run FlightNode locally:
Make local copies of all the repositories mentioned in the Architecture
page. Be sure to configure an upstream remote and follow the workflow
described in Git Tutorials, Workflow, and GUI.
Open the FlightNode.Identity solution in Visual Studio 2015. Open the
Package Manager Console (menu: Tools > NuGet Package Manager > Package Manager Console).
Who did this? Who would leave such mighty poo below my bell pepper? Our fence is too tight for rabbits...
Updated 2021-05-25
Git is a fabulous tool for source control management. While incredibly powerful, it can be a little daunting to learn at first. The following tutorials will help. They are organized from basic to more advanced.
