nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Another possibility: did you perhaps change nunit's config file as
recommended in many posts to deal with loading of mixed dlls?

In any case, I'm closing the bug using "Invalid" status - I wish there
were a less severe status like "Out of date."

** Changed in: nunitv2
       Status: New => Invalid

** Changed in: nunitv2
     Assignee: Charlie Poole (charlie.poole) => (unassigned)

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

Title:
  Mixed dlls won't load on Windows 7

Status in NUnit V2 Test Framework:
  Invalid

Bug description:
  From a QUESTION posted in NUnit's Answers section on Launchpad...

  I couldn't report this using Launchpad, so I'm putting it here.

  Problem: Can't run a test dll which references mixed C++/CLI dll's
  which reference native C++ dll's. Said test dll runs fine in Windows
  XP, but not in Windows 7.

  1) [XP Box] I build the test successfully
  2) [XP Box] I run it from the command line using nunit-console (by the way, both boxes use NUnit 2.5.9, installed with the same .msi file, and both Windows are 32 bit ones). Runs fine.
  3) Copy the folder with all dll's to the Windows 7 box.
  4) [7 Box] Same as 2, but using the copied dll's. Fails with this message: "Could not load file or assembly <C++/CLIAssembly>.dll or one of its dependencies. The specified module could not be found."

  I tried enabling fusion logging to see where was NUnit seeking the
  offending dll, but no binding failures related to it where logged.
  Only some from nunit, but I guess those are normal.

  I checked if my XP box had any different setting in its PATH
  environment variable, but not.

  So now I'm stumped :(

  Cheers and thanks for your time

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