A major refresh

[nblumhardt]

While Seq Forwarder is a critical piece of the Seq ecosystem, we've had difficulty maintaining forward momentum on this project:

• Only Windows and .NET Framework were supported, making it harder for us (often working on macOS or Linux) and the community to contribute,
• WPF and Windows Installer are both awkward to work with, even on Windows,
• We've been unsure about the best distribution of features between Seq Forwarder and seqcli.

This PR is a line in the sand - a bit of a fresh start - that modernizes the codebase and trims it back to the bare essentials necessary to meet Seq Forwarder's goal, which is:

Local collection and reliable forwarding of log data to Seq

To get there I've:

• Removed the Windows installer
• Removed the WPF-based setup wizard
• Removed the file-based import command - seqcli does this better
• Renamed the executable to seqfwd, since setup is now via the command-line, and we'll type this a lot
• Ported to .NET Core 3.1
• Replaced NancyFX with ASP.NET Core
• Added support for macOS and Linux
• Set up zip/gzip release publishing
• Added support for compact log event format (CLEF), aka compact: true
• Added support for SSL certificate binding on Windows

Some of these items will be a step backwards, but, by simplifying the project and improving the development experience we can put our effort into improving the features, efficiency, reliability, and manageability of the core log forwarder.

Fixes #16, fixes #21, fixes #49, fixes #50

[darrynparker]

Yep - this looks great and I love the .Net Core implementation. I had a look over the weekend and so far it fills the gap......but the only other feature gap is the capability of the original consuming application to have it's own Seq API key also forwarded to the Seq server.

Apart from that - well done.

[nblumhardt]

Hi @darrynparker - thanks for taking a look!

I just tried out API key forwarding and it still works for me using the 2.0 preview release - if you're finding otherwise, it would be great to have a bug report (I could be missing something :-) )

Thanks!

[darrynparker]

OK - thanks, I'll check it out.