From: Bergman, M. <MBe...@nd...> - 2006-11-23 09:18:54
|
Hello, =20 I saw this thread on the archive, and I just ran into the same problem. Has anyone managed to solve this? =20 Original Therad: Sorry I've not been back to you. =20 There only appear to be two forms of the attribute according to MSDN. One with a public key (both assemblies must be signed) and one without the key (when neither is signed). =20 Neither can be coerced into solving the problem. =20 Thanks =20 =20 -----Original Message----- From: nmock-two-dev-bounces@li... [mailto:nmock-two-dev-bounces@li...] On Behalf Of Steve Mitcham Sent: 18 August 2006 15:31 To: NMock2 Development Discussion Subject: Re: [NMock2-Dev] Access is denied on internal interfaces? =20 You need to add the fully qualified signed assembly name with the version and public key token to make it work. Don't know what that is off the top of my head. =20 _____ =20 =20 From: nmock-two-dev-bounces@li... [mailto:nmock-two-dev-bounces@li...] On Behalf Of David Webster-Jaggard Sent: Friday, August 18, 2006 8:41 AM To: 'NMock2 Development Discussion' Subject: Re: [NMock2-Dev] Access is denied on internal interfaces? =20 Wow you're up early! :-) =20 I added this line to the test project to make NMock2 a friend =20 [assembly: InternalsVisibleTo("NMock2")] =20 It didn't help although it seems like it should. Any idea why not? =20 Thanks =20 -----Original Message----- From: nmock-two-dev-bounces@li... [mailto:nmock-two-dev-bounces@li...] On Behalf Of Steve Mitcham Sent: 18 August 2006 14:23 To: NMock2 Development Discussion Subject: Re: [NMock2-Dev] Access is denied on internal interfaces? =20 Making Nmock2 a friend assembly would work. You could also have a conditional compilation flag that made them public when built for testing purposes. However, I think the value of testing internal interfaces directly is limited. _____ =20 =20 From: nmock-two-dev-bounces@li... [mailto:nmock-two-dev-bounces@li...] On Behalf Of David Webster-Jaggard Sent: Friday, August 18, 2006 8:09 AM To: nmock-two-dev@li... Subject: [NMock2-Dev] Access is denied on internal interfaces? =20 I'm upgrading our unit tests to NMock2 and have come across a bit of a problem. If I try to mock and internal interface I get an access denied error when I run the test. Here is some example code: =20 using NMock2; using NUnit.Framework; =20 namespace NMock2Test { internal interface IInternalInterface { void DoNothing(); } =20 [TestFixture] public class Class1 { [Test] public void Test() { Mockery mocks =3D new Mockery(); IInternalInterface mockInterface =3D mocks.NewMock<IInternalInterface>(); } } } =20 Is there anyway to get around this (maybe make NMock2 a friend assembly, however you do that..)? I don't want to start making internal interfaces public. =20 Thanks Moshe Bergman *************************************************************************= ********** This email message and any attachments thereto are intended only for use = by the addressee(s) named above, and may contain legally privileged and/o= r confidential information. If the reader of this message is not the inte= nded recipient, or the employee or agent responsible to deliver it to the= intended recipient, you are hereby notified that any dissemination, dist= ribution or copying of this communication is strictly prohibited. If you = have received this communication in error, please immediately notify the = pos...@nd... and destroy the original message. *************************************************************************= ********** |