Ok, I got latest on the Moq trunk and applied that to my version of the silverlight build however ran into a couple snags...1. Indy.IL2CPU.IL.ILReader contains a reference that gives me the following error.Error 6 'System.Reflection.MethodBody' is inaccessible due to its protection level C:\Code\moq-dev2\moq\Source\IL\ILReader.cs 24 20 Moq.Silverlight2. I get the following error when I comment the code above that is not compiling.Error 6 'System.Reflection.Module' does not contain a definition for 'ResolveField' and no extension method 'ResolveField' accepting a first argument of type 'System.Reflection.Module' could be found (are you missing a using directive or an assembly reference?) C:\Code\moq-dev2\moq\Source\IL\ILReader.cs 149 54 Moq.SilverlightI see that the ILReader was checked in to support issue 130. Maybe we can look at not having that feature in silverlight by wrapping some compiler if/endif's around that? Or is there another way?
Given the above, I also don't have up-to-date tests.I'd like to leverage the same test .cs files in a different silverlight project that just link back to the original files. However xUnit doesn't exist in silverlight. Jeff Wilcox from Microsoft had a blogpost about how to plug in a ported NUnit to leverage the browsers silverlight testing harness, however I don't want/have time to port xunit like this.
I have an idea, but don't want to put the time unless you're ok with this idea because it would require modifying all the assertions in the main testing project.One suggestion would be to follow something like this in my blog http://staxmanade.blogspot.com/2009/02/fluent-specification-extensions.html to abstract away the assertions. This way we could have different testing frameworks implementing the assertions (xunit for full framework, Microsoft.Testing.Silverlight for the silverlight version).
It would basically mean cutting functionality out :(
/kzu from mobile
--~--~---------~--~----~------------~-------~--~----~ Post: moq...@googlegroups.com Unsubscribe: ...