[Mono-dev] NUnit shadow copy and multiple users issue

Michael Franz mvfranz at gmail.com
Sun Feb 16 20:56:02 UTC 2014

On Sun, Feb 16, 2014 at 12:34 AM, Michael Franz <mvfranz at gmail.com> wrote:

> Hi,
> I have been setting up my development environment on CentOS 6.5 and have
> had some great success.  My latest issue is temp directories and shadow
> copies while running nunit.  The issue is documented here and fixed in
> NUnit 3.0 https://bugs.launchpad.net/nunit-3.0/+bug/719187 .  Is there
> any plan to upgrade the Mono version of NUnit?
> I might be wrong, but I have only been able to get the version of NUnit
> that is embedded in Mono to work for me.  Is there a way that I can upgrade
> my local copy and have it still work?
> Or, is the best way to resolve this issue is to create a patch for the
> shadow copy logic for the Mono version of NUnit?
> Michael
After looking into a fix for this, it seems that the easiest fix is to
change the nunit-console-exe.config files (I found 4) and one App.config.
 I am not sure which ones actually need to be changed as I don't fully
understand the build and install process.  It actually took a lot of
searching to find all of them.

# modified:   mcs/nunit24/ConsoleRunner/nunit-console-exe/App.config
# modified:
# modified:
# modified:
# modified:   mcs/tools/linker/Tests/Libs/nunit-console.exe.config

The patch for all is the same, it creates a user specific temp directory
for running unit tests.  This works for my setup, as I run multiple users
on the same machine.
I am sure there are better ways to resolve this issue, this just seem like
the easiest.

-    <add key="shadowfiles.path" value="%temp%\nunit20\ShadowCopyCache" />
+    <add key="shadowfiles.path"
value="%temp%\nunit20-%USERNAME%\ShadowCopyCache" />

What is the best way to proceed?

I also looked to raise a bug for this in the Mono bug database, but not
sure what component the NUnit code is under.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140216/74e4c09c/attachment-0001.html>

More information about the Mono-devel-list mailing list