Silverlight 4 And Resharper 5 = Pain

I’ve been a longtime fan of Resharper and pretty much don’t even want to use Visual Studio without it.  But we’re in the process of upgrading to Visual Studio 2010, Resharper 5, Silverlight 4 and (later on) .NET 4 and yesterday we made a bit of a painful discovery.  It turns out that using Resharper 5 in Visual Studio 2010 actually makes your development experience worse than it is by default if you’re using Silverlight 4. 

The first problem is this:

If you use Action a lot in your code (and we do) then you’re pretty much screwed.  Resharper doesn’t recognize it and continually suggests changing it to a generic type.  Now, you can just press escape and go on working but it’s still very, very annoying.

Another thing that’s highly annoying is this:

This is valid code, but Resharper doesn’t quite agree with us…  Which of course also makes solution-wide analysis completely useless:

And this is in a solution which actually has no real errors whatsoever.

This should be fixed in Resharper 5.1, but unfortunately, that won’t be out until June.  We can only hope that the EAP builds of 5.1 start showing up ASAP because this situation really sucks for those who’re working with Silverlight 4.

So in case anyone of Jetbrains is reading this: please hurry up and get those EAP builds out the door so we can start using (and enjoying) your product again