Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Does NCrunch support Probing paths?
rubik
#1 Posted : Wednesday, October 30, 2019 7:48:20 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 10/30/2019(UTC)
Posts: 1
Location: United States of America

Hi,

I'm new to NCrunch and trying to determine if it's a good fit for my team. I'm finding there are a lot of configuration options, but I can't seem to find the right one to make it work for my projects.

As background, for various reasons we move all the referenced dll, pdb, and xml files from our output directory into a library folder. This is accomplished by setting
Code:
  <probing privatePath="library" />

in the app.config. This keeps our output folders cleaner, as our end users have to muck about a bit in with various configuration settings to get our product running. This doesn't seem to have any downsides in Visual Studio, as it easily finds the relevant files for debugging or whatever else.

In my testing, it doesn't appear NCrunch is capable of honoring the probing setting, and therefore won't run without me restructuring my solution. Am I missing a flag somewhere?

Example File Hierarchy:
Code:

MySolution/
  MyExecutableProject1/
    bin/
      debug/
        MyExecutable.exe
        library/
          MyExecutable.pdb
          MyDependency.dll
          MyDependency.pdb
          externalDependency.dll
  MyDependency/
    bin/
      debug/
        MyDependency.dll
        library/
          MyDependency.pdb
Remco
#2 Posted : Thursday, October 31, 2019 12:13:28 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,830

Thanks: 754 times
Was thanked: 973 time(s) in 927 post(s)
Hi, thanks for posting!

This particular feature isn't supported by NCrunch, as it completely breaks the referencing system we use to short-circuit the builds, which allows them to complete in a fraction of their normal time.

Sorry, other than restructuring your referencing, I can't think of an effective workaround for this without manually loading the assemblies at runtime using Assembly.LoadFrom inside your test code (which would completely negate the purpose of the probing path).
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.035 seconds.