I think I understand the problem now: strong-named assemblies can not
declare their internals to be visible to not-strong-named assemblies.
Thus,
- for mocking not-strong-named assemblies, I would need a build of
NMock that uses InternalsVisibleTo("DynamicProxyGenAssembly2"),
- whereas I would need a build of NMock that uses
InternalsVisibleTo("DynamicProxyGenAssembly2, PublicKey=...") to mock
a strong-named assembly.
I think I'll just go ahead and create two different builds of NMock
for my project. I prefer that to possible collisions with the Castle.
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
