Category Archives: mono

Touch.Unit vs NUnitLite 1.0

In case you have not noticed NUnitLite has picked up speed in the last few months. Xamarin.iOS 7.0 shipped with NUnitLite 0.9 – itself announced right before WWDC2013, i.e. when the 6.9 series began its summer-alpha life. Then just a … Continue reading

Posted in mono, monotouch, touch.unit, xamarin | 2 Comments

Random Changes

and by random changes I mean changes to Random. Here’s what’s affected by the change: Performance The old algorithm used by Mono was not very efficient, even less on system where floating-point computations are slow. The new algorithm, JKISS, is … Continue reading

Posted in mono, monotouch, xamarin | 2 Comments

Graphics vs Resolution Independance

I love my retina iPad (and retina iPod Touch, but no retina MacBook yet) and I hate seeing applications that does not support them, it’s wasting pixels. However I’m not exactly an artist – as seen in yesterday’s screenshots. In … Continue reading

Posted in mono, monomac, monotouch, xamarin | 3 Comments

AirPlay vs iOS API

This post should not be a big surprise. As you might have guessed I had other ideas with my AppleTV. I think there’s a large, untapped potential in the AppleTV to be used with/from other devices. Collaboration, visualization and of … Continue reading

Posted in airplay, appletv, mono, monotouch, xamarin | 4 Comments

AirPlay vs Large Digital Frame

We (as a family) have been looking for a large digital frame. My wife takes a lot of pictures (mostly kids and vacations) and showing them was always… less than optimal. We have a few, small 7-8 inches, digital frames … Continue reading

Posted in airplay, appletv, mono | 3 Comments

Touch.Unit vs NUnitLite 0.7

Last week Charlie Poole released NUnitLite 0.7. This new release greatly reduce the feature gap between the older 0.6 release and the upcoming NUnit 3. I know people will rejoice having Assert.AreEqual(x,y) back as it is simpler than the Assert.That … Continue reading

Posted in mono, monotouch, touch.unit, xamarin | Leave a comment

Linker vs Bindings and IsDirectBinding

If you looked at my previous entries related to the linker and bindings: NewRefcount, UI thread checks, Runtime.Arch or at MonoTouch‘s generated bindings source code then you likely noticed another common pattern, e.g. The use of IsDirectBinding (line #6) is … Continue reading

Posted in linker, mono, monotouch, xamarin | Leave a comment

Managed Crypto vs CommonCrypto : Deciphering results

After the hash algorithms the next part of MonoTouch‘s switch to CommonCrypto covers the symmetric ciphers, commonly referred to CommonCryptor. This includes: DESCryptoServiceProvider, TripleDESCryptoServiceProvider, RC2CryptoServiceProvider and parts of RijndaelManaged inside mscorlib.dll; ARC4Managed inside Mono.Security.dll; and AESManaged inside System.Core.dll Those are … Continue reading

Posted in crimson, crypto, mono, monotouch, xamarin | Leave a comment

Managed Crypto vs CommonCrypto : Digesting results

As part of MonoTouch‘s switch to CommonCrypto most of the digest (hash) algorithm implementations were changed to use CommonDigest. This includes: MD5CryptoServiceProvider, SHA1[CryptoServiceProvider|Managed], SHA256Managed, SHA384Managed and SHA512Managed inside mscorlib.dll; and MD2Managed, MD4Managed and SHA224Managed inside Mono.Security.dll If you know well … Continue reading

Posted in crypto, mono, monotouch, xamarin | 1 Comment

Managed Crypto vs CommonCrypto

A bit of history… Mono has always provided fully managed implementations of almost every cryptographic algorithms supported by .NET, either directly (in the base class libraries) or indirectly (e.g. additional algorithms required for X.509 or SSL/TLS support). That approach gets … Continue reading

Posted in crimson, crypto, mono, monotouch, xamarin | 2 Comments