FubarCoder

What about Spellbound Spire? Maybe it's something for you.

Intel syntax is an x86 thing.

The main feature - for me - was the ability to use the same project.json to compile a project for multiple frameworks. Sad to see, that they ditch project.json - especially after the overhaul one or two weeks ago, which was a necessary cleanup. How will they be able to release the rc2 on May, 16th, week they change a critical part of the build chain again? Does this mean, that they are ditching dotnet CLI too?

This is the core functionality of a product I made for a customer. He has two legacy applications that only support backup using FTP servers, but he wanted to store those backups on Google Drive.

The challenging part was the upload to Google Drive while still looking like a normal standard compliant FTP server and running as Windows Service.

The core FTP server library is written as PCL. The underlying Google Drive library uses RestSharp.Portable which is also available as PCL and should allow the use in .NET Core, Windows Store, and Xamarin projects.

This is a hand-made port of BeanIO from Java to .NET which was changed in the following aspects:

* Support of .NET generics

* Availability as PCL (.NET 4.5, Win8, Win Phone 8.1, Xamarin.iOS/Android)

* Scheme handlers to support loading of mappings from any place

* Available as NuGet package

All original unit tests were ported (over 300) and should therefore mostly behave in the same way as the original BeanIO project.

We use C++/CLI, because it's the easiest way to use .NET components together with legacy MFC code.