nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

It will not be quite so easy as that. :-(

In some places, we have to use Assembly.Codebase, because Assembly.Location
can up being in the Shadow Copy Cache and we need the actual directory in
which the assembly originally located in order to navigate the directory
structure using relative paths. 

In NUnit 2.x, we parsed the location ourselves to resolve the # issue and may
have to do the same in NUnit 3.0. However, the best approach would be to 
try to eliminate the need for the actual directory in the code.

This is a good catch - I guess I forgot why we had all that code in 2.x
in the first place!

Charlie

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/928246

Title:
  Use assembly.Location instead of assembly.CodeBase

Status in NUnit Test Framework:
  Triaged

Bug description:
  Some areas of NUnit uses assembly.CodeBase instead of
  assembly.Location. Because of that NUnit fails to resolve assemblies
  when the path contains #. This is because CodeBase is a Uri.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/928246/+subscriptions