Anyone using Silverlight.FX with Silverlight 3?
I started looking at Nikhil Kothari's Silverlight.FX to replace Prism / Unity with our Silverlight 3 project.
So far, I like the layout and structure of the code. It looks well thought out.
But I cant get many samples working due to System.Reflection.AmbiguousMatchException. Has anyone else seen this? Should I use this framework for Silverlight 3?
a source to share
After some heavy debugging, this error comes up because some of the class names used by Nikhil I believe are now in Silverlight 3 beta 1. The TaskList example in the DataTemplate ListView has a HoverEffect
<fxeffects:ColorFill FillColor="#406795D1" Duration="0:0:0.25"/>
This is the one that is causing all the problems I have seen. When removed, this threw an AmbiguousMatchException.
a source to share
Well, that means avoiding this problem, not solving it. It looks like the problem goes much deeper, and anything that uses classes that derive from the base Effect class is being violated. This makes Silverlight FX pretty boring.
I have tried using lib in the past and have had problems with it. While Nikil Kothari is amazing at what he has worked on and his technical ability, I find that he is not that responsive to problem solving (BTW, someone already posted this issue on his blog, without his answer) ... I don't want this to sound like a knock on Nikhil, it's just something that you need to consider when using open source for real projects.
I'm sure someone can figure out what the deal is with these classes, I've spent many hours debugging without solving the problem.
a source to share
I tried the Amazon Store sample and the TaskList sample using the latest version of the library (3.1 built against SL3) and the samples seem to work fine including the ColorFill effect.
I renamed the Effect class to AnimationEffect, which is what you need to avoid the ambiguous API compilation error you see if you try to recompile the sources ... but the precompiled binaries would be fine. Not sure if I can see why you are having runtime playback issue.
Sorry, I know it might be frustrating not to see the answer / fix right away, but theres too many things going on esp. before release. My hope is that the source around at least allows you to debug / break so that at least one of them is not completely blocked. Yes, I understand its suboptimal, but at the same time it is reality as Noam pointed out ...: --(
a source to share