lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Herndon <>
Subject Re: Why the use of Utils.Paths in TestBackwardsCompability?
Date Sun, 29 Jul 2012 18:20:15 GMT
because of the shadow copy feature in nunit.

simply using
Path.Combine("Index", "index." + oldNames[i]);

won't work when the test assemblies are located in funky places.

On Sun, Jul 29, 2012 at 4:56 AM, Simon Svensson <> wrote:

> I'm looking into running the tests in MonoDevelop (Mono 2.10.9) on a Mac,
> debugging one failure at a time. The TestBackwardsCompability tests fails
> when unzipping because the paths for the source zip files are incorrectly
> calculated. It originates in Paths.AssemblyDirectory, where it returns a
> rooted path on Windows ("C:\Users\sisve\..."), but a relative path on Mac
> ("Users/sisve/...").
> We could use the existing Path.Combine, and choose to copy to
> files to the output directory. This would remove  the need
> for the Paths class completely [if I understand it correctly]. (It's also
> used from LuceneTestCase to initialize a variable no-one uses.)
> Old: System.String dirName = Paths.CombinePath(Paths.**ProjectRootDirectory,
> "test/core/index/index." + oldNames[i]);
> New: System.String dirName = Path.Combine("Index", "index." + oldNames[i]);
> But this makes me wondering, why was the Paths class introduced at all?
> // Simon

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message