nunit-core team mailing list archive

[Michael Ketting <746247@xxxxxxxxxxxxxxxxxx>]

Hi Charlie!

Yes, the only immediate need is the nunit.framework assembly. We're
using reflection to discover the TestFixtures and Test-methods since our
tests are simple enough and don't take advantage of the more
sophisticated nunit features.

Regarding the other assemlies: I've taken a quick look around and yes,
it would be nice if you would also mark nunit.core.interfaces,
nunit.core, and nunit.util as partially trusted. In the end, a nice,
attribute (or the likes) syntax would be great, with which one could
specify a test fixture to run in a partially trusted sandbox with a set
of permissions specified by the test author. From the (very quick) look
of it, RemoteTestRunner might actually be already half-way there. If
there's time, we'll likely take a closer look at it and see if it's
possible to come up with either an extension or a non-intrusive patch.

Thanks, Michael

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/746247

Title:
  Add  AllowPartiallyTrustedCallersAttribute to nunit.framework assembly
  to allow use in medium trust scenarios

Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  /well, it's not a bug, it's a feature request/

  Please consder adding the  AllowPartiallyTrustedCallersAttribute to
  the nunit.framework assembly. We're running certain integration tests
  in a medium trust scenario to ensure compatibility of our library in
  these cases and right now, have to make a custom build of
  nunit.framework to enable this. The only alternative is to forgo the
  nunit asserations, but we've really come to like them ;)

  Regards, Michael

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/746247/+subscriptions