I just released the first pre-release bits for WP7 support in Ninject. You can download them here. If you encounter any issues, please let me know. I have included signed and unsigned binaries in debug and release configurations.

Unit testing isn’t very easy for WP7. It was bizarre trying to debug the issues. The exact code that returns whether one type is assignable to another returns false in WP7. If you are trying to target WP7 and are familiar with Silverlight, you need to check out this site to see what may hurt you; the section on reflection is rather painful. These are two of my favorites:

• Open generics are not supported in Silverlight for Windows Phone.
• The equality (==) operator for two equal MethodInfo objects does not return true in Silverlight for Windows Phone.

One thing to note is that this code is directly off the master branch for the 2.1 release. The 2.1 release has an enhanced resolution algorithm that may be a little different that what you previously expected – if you get an exception, you were most likely doing something ambiguous that Ninject wants straightened out. I will be blogging more about this later, but the binding resolution should now better handle what you are asking it to do.

I will be making blog posts to more than one blog from now on. If you take a look at the IntelliTechture blog you can use the main feed or my personalized feed to see my blog posts that are not posted here. I just blogged on Parallel.For where i does not go to i++ in which I create an iterator to allow us to move forward, backward, skip, and use a wide variety of types in our sequences.

I am happy again to announce the release of the next Ninject extension, Ninject.Extensions.MessageBroker 2.0! You can download the release from GitHub for all supported platforms (.NET 3.5, .NETCF 3.5, SL2, SL3, MONO). Also, you can review the demo post using the extension if you are wondering how to hook it together.

On the heels of the Ninject 2.0 release, I am happy to announce the release of the Ninject Interception Extension 2.0. This release provides API backward compatibility for the 1.5 version as well as new method interception, enhanced binding syntax, automatic property changed notification, as well as support for Castle DynamicProxy 2.2 and LinFu DynamicProxy. I will be writing a follow up post about the new features and usage patterns.

I want to thank Krzysztof Koźmic for his help with the Castle DynamicProxy 2.2 integration and Michael Hart for letting me merge his Ninject 1.5 method interception code into the new extension.

You will find downloads on the GitHub dowload page for .NET 3.5, Silverlight 3, and Mono 2.0. For those using automatic module loading or only want to use one DynamicProxy dependency without worrying about delay loading, there are three .NET 3.5 downloads: Castle+LinFu, Castle, and LinFu. Go get it!

That’s right! We have officially released Ninject 1.5 and 2.0! Ninject 2.0 has been in beta for exactly one year and we are very happy to announce its release. You can download the binaries from the Ninject.org web site. Expect more posts here and on Nate’s blog with more information.

Over the next couple weeks we will be releasing the extensions projects based on the official 2.0 release for all available platforms. The 1.5 wiki is up and the 2.0 wiki documentation is in process including changes between the versions.

Nate has the official announcement out!

Seeing that people wanted to use Castle DynamicProxy2 with Ninject for interception, I ported the support from Ninject 1.5 and we now have support for using DynamicProxy2 built-in for the Ninject 2.0 extension.

DynamicProxy2:

IKernel kernel = new StandardKernel(new DynamicProxy2Module());

LinFu:

IKernel kernel = new StandardKernel(new LinFuModule());

Note: Breaking Change!!!
InterceptionModule is now abstract. The proxy specific modules need to be used now. This base module is used to wire up the interception pipeline leaving inheritors to only registry proxy factories.

It has been quite a while since I last blogged. In usual style, it has been for a reason seen over and over. I changed jobs.

I have started my own software company doing contract .NET development as well as partnering with IntelliTechture. It has been very hectic switching from employee to business owner and great experience. Now that things are calming down a bit I anticipate that I will be blogging regularly again.

You can now build Ninject for both the 1.X and 2.0 code bases with Horn now. I would like to thank the Horn developers and mailing list for answering my questions and lending a hand.

If you haven’t heard of Horn, you should definitely check it out. Taking Horn for a test drive is a great getting started article. To install Ninject using Horn is pretty easy:

// install Ninject 1.X
horn -install:ninject

// install Ninject 2.0
horn -install:ninject -version:2.0

You will notice that Ninject 2.0 will compile a lot faster than 1.X as it does not have the Castle dependencies that the Ninject 1.X code base has. Very cool stuff. I always liked portage in Gentoo Linux; I am happy that it has a .NET sibling now.

I have been waiting for this for a long time. There is a private preview for tools that will allow you to write .NET apps and port your code at the same time. It looks like they integrated the compatibility analyzer, remote Linux debugger, packaging system and local mono debugging into Visual Studio. It is too bad this didn’t come out while I was writing code for Linux.

The Ninject 1.X repository has been migrated to GitHub; However, this version is only receiving critical bug fixes, all new development is being done on the Ninject 2.0 codebase. We will be releasing 1.5 pretty soon, so if you need to use Ninject 1.X for compatibility, keep an ear open.