http://ayende.com/Blog/archive/2007/10/26/Rhino-Mocks-killed-Visual-Basic.aspx
I also used NMock2 for a time, but ran into an issue where the
assembly wasn't strong-named; therefore, I couldn't use it to test my
strong-named production assembly. I also didn't like having to define
the method name as a string -- because I lost compile-time support if
I needed to refactor (rename the method).
So, today I use NUnit.Mock. It works for basic scenarios, but I also
have the issue of using strings to specify my mocked methods. I
haven't tried Moq, but heard that it has the same compiler issue as
Rhino Mocks.
http://groups.google.com/group/moqdisc/browse_thread/thread/db59f09611292967
So, for those of you that are VB.NET TDD folks, what do you recommend
as a good Mock Object framework?
Thanks,
Matt
--
You received this message because you are subscribed to the Google Groups "Test Driven Development" group.
To post to this group, send email to test-driven...@googlegroups.com.
To unsubscribe from this group, send email to test-driven-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/test-driven-development?hl=en.