This project is a POC to determine the plausibility of writing a .NET Standard library and using it across devices INCLUDING WebAssembly (WASM). The root library, Asteroids.Standard, encapsulates all logic for rendering the classic '80s video game. None of this is meant to be production-worthy. It is more me just messing around trying to see what works.

The original code was adopted from a very cool WinForms project on CodePlex by Howard Uman, circa 2004:

https://www.codeproject.com/articles/7428/c-asteroids

It was chosen because it was already in C# and very straight forward in terms of inheritance and logic. Separating the logic from the UI layer was relatively simply.

Currently, the project is made of the following:

• Asteroids.Standard - .Net Standard Library containing the game engine.

• Asteroids.WinForms - Reconstructed WinForms GUI that uses the game engine with a PictureBox as the main renderer.

• Asteroids.Wpf - Equivalent WPF GUI to the WinForms applications that uses a WPF WriteableBitmap as the main renderer with help from the WritableBitmapEx library.

• Asteroids.Xamarin - The core Xamarin application that uses SkiaSharp for 2D rendering via a SKCanvasView.

• Asteroids.Xamarin.Android - Android GUI that uses the core Xamarin library.

• Asteroid.Xamarin.UWP - UWP GUI that uses the core Xamarin library.

• Asteroids.Blazor - WASM project that uses Microsoft's experimental Blazor to allow cross-compiling the C# code to WASM so it can be rendered in a browser (see below for more info).

• Asteroids.BlazorComponents - Blazor library that contains the actual game engine instantiated object and associated HTML and JavaScript bridge to allow rendering in the browser.

All applications are written in Visual Studio so they can be launch simply by doing Debug -> Start New Instance. The Android application will need some additional configuration like any other Xamarin project, e.g. I test in an Oreo VM running on my dev machine.

All applications are fully functional at this point in terms sound and keyboard support. Performance varies among the technologies with the UWP app being the clear winner for desktop and Firefox for Blazor/Web.

There is no Xamarin iOS app at this point only because Apple does not allow development on non-macs (which is what I am on) without connected hardware. But there is no technical reason for it not to be possible.

The UWP application is set to require the Windows 10 Fall Creators Update at a minimum. This is necessary to run the latest .NET Core and Standard versions.

Microsoft has labeled Blazor as "experimental" (as of the time of this writing) and, as such, has allow themselves the luxury to break anything at any time :). So, version control will be important when trying to build and run this app. To build the app, simply do it from Visual Studio - just make sure you have all dependencies listed on their GitHub page. If Visual Studio 2017 hangs occasionally when trying to build, do Ctrl+Shift+S to get around a bug that existed in some version or get the latest update. Doing it from CLI in the Asteroids.Blazor project folder is also an option:

dotnet build

To run the application, simply hit F5 or ctrl+F5 in Visual Studio or from the CLI:

dotnet run

If you get an HTTP 502.5 error, chances are there is a mismatch in the installed SDK vs what is listed in the global.json file in Asteroids.Blazor:

"sdk": {
    "version": "2.1.400.1"
  }

To find your version run:

dotnet --version

and update the json to match. Or install the above version since you can have more then one simultaneously.