DotNetKicks.com : Stories kicked by jpobst

Static Method Interception in .NET with C# and Mono.Cecil

Sat, 02 May 2009 02:01:02 GMT

Interested in Mono.Cecil? A very short introduction to a very cool and powerful tool.

Using MoMA to Port from .Net to Mono

Fri, 17 Apr 2009 05:59:51 GMT

Describes how you can use MoMA to test your .Net application's readiness to run on Mono.

Novell's Mono brings SIMD support to C#

Wed, 08 Apr 2009 21:31:21 GMT

Parallel programming is not just about multi-threading and multi-core. There's also a lot of power in the SIMD (Single Instruction Multiple Data) extended instruction set available in most modern microprocessors from Intel and AMD. From Dr Dobb's Go Parallel blog.

Getting Mono and Visual Studio to play nice together

Wed, 18 Feb 2009 02:16:12 GMT

The goal was to get some Mono project templates working with Mono assemblies and the Mono compiler in Visual Studio. The trick was to do it in a way that would be able to survive upgrades of Mono installations.

Moonlight 1.0 Release

Thu, 12 Feb 2009 20:16:03 GMT

Now Linux lovers can enjoy Silverlight streaming media with Moonlight 1.0. Read what Scott Guthrie tells us about this open source implementation of Silverlight.

Moonlight 1.0 Release - Open Source Silverlight 1.0 Implementation on

Thu, 12 Feb 2009 10:15:10 GMT

Scott Hanselman talks about Moonlight 1.0.

Mono 2.0 Released

Tue, 07 Oct 2008 02:01:15 GMT

The Mono Project has released version 2.0 of Mono, enabling developers to run their .Net 2.0 applications on Linux and OSX.

LINQ Expression Trees on the Compact Framework

Tue, 23 Sep 2008 05:53:56 GMT

A week ago, I was writing about the ability to use Mono's System.Core to run C# 3 and LINQ applications on .net 2. A few months ago, I was writing about the new LINQ provider that friends at db4o released. This LINQ provider uses LINQ expression trees to optimize LINQ queries, turning them into db4o's native query language. Today I'm going to write about a cute new hack from our friends at db4o. If the 3.5 version of the Compact Framework comes with a System.Core, and a LINQ to objects implementation, it doesn't contain the namespace System.Linq.Expressions, which is used by all optimized LINQ providers. What those fine folks did, was simply to take Mono's implementation of this namespace. There was one issue with that approach. Expression Trees can be compiled at runtime, and that uses System.Reflection.Emit, that the Compact Framework doesn't have. A nice thing is that folks at Mainsoft contributed to Mono's System.Core an expression interpreter, which allows you to use the full LINQ expression trees without using System.Reflection.Emit. They sent me the patches they have for the expression interp