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.
Here is a a brief demonstration of authentication and authorization using the FlightNode.Identity API. Significant help developing this received from ASP.NET Identity 2.1 with ASP.NET Web API 2.2 (Accounts Management) by Taiseer Joudeh.
Requires cloning the FlightNode.Identity and FlightNode.Common repositories.
Once upon a time, not far from downtown high rises, the greens and ponds of a golf course took over a portion of forested river bottomland. The river, having a mind of its own, would periodically flood out the golf course. The players complained about the mosquitoes and the stench of sewage from the treatment plant not far upstream.
Concerned about the quality of the water, and needing an outlet to lower the river's flood levels near downtown, someone decided to do something. The City took over the courses, much to the unfortunate owner's chagrin, and partnered with experts to remake the land. Where fairways once stood, now wetland ponds flow, further cleaning the already-treated waters. The greens were pulled up and natives plants installed, leading to a beautiful renaissance of prairie grasses, wildflowers, and their marshy kin too.
Tropical Mockingbird, Hopkins, Belize. 2014, Stephen A. Fuqua.
The general problem, succinctly stated:
As human-dominated land uses replace native landscapes across North America, there is growing concern about the impacts this habitat loss will have on native bird populations. With many migratory bird species in decline, it is essential to assess the effectiveness of our conservation initiatives [1].
Of course, this applies around the world, not just in North America. There are hundreds of organizations and researchers working to understand the characteristics of current bird populations, and our impact on sustaining and growing those populations. The need for this work grows ever more pressing for those who recognize the value of maintaining diverse and vibrant ecosystems, especially in light of climate change [2].
