The .NET runtime had collected a few cobwebs the past few months. I spent some time this week bringing it back up-to-date. .NET support lags the JVM, but as long as we keep the core runtime and sys library up-to-date with Java, we know Fantom remains portable across our three official platforms. And once there is a community need for .NET, hopefully they can spend some time helping us flush out proper support.
So if anyone plays around with Fantom on .NET and sees something broken across builds - let us know so we can make sure it wasn't a regression bug, and/or if its an easy fix.
andy Thu 11 Feb 2010
The .NET runtime had collected a few cobwebs the past few months. I spent some time this week bringing it back up-to-date. .NET support lags the JVM, but as long as we keep the core runtime and sys library up-to-date with Java, we know Fantom remains portable across our three official platforms. And once there is a community need for .NET, hopefully they can spend some time helping us flush out proper support.
So if anyone plays around with Fantom on .NET and sees something broken across builds - let us know so we can make sure it wasn't a regression bug, and/or if its an easy fix.