NUnit assembly not found

前端 未结 5 1540
被撕碎了的回忆
被撕碎了的回忆 2021-02-02 12:25

I\'ve used NUnit before, but not in a while, and never on this machine. I unzipped version 2.4.8 under Program Files, and I keep getting this error when trying to l

相关标签:
5条回答
  • 2021-02-02 12:50

    Note that the current NUnit installation (2.5.10) doesn't register itself automatically in the GAC.

    If you must use GAC, register it via gacutil /i <nunitframeworkpath> where nunitframeworkpath is usually %Program Files%\NUnit\net-2.0\framework\nunit-framework.

    0 讨论(0)
  • 2021-02-02 12:57

    If you install using NUnit-2.4.8-net-2.0.msi, the NUnit assemblies are added to the GAC.

    You can also reinstall manually by running gacutil from the Visual Studio 2005 command prompt.

    0 讨论(0)
  • 2021-02-02 13:01

    Make sure you have added a reference to nunit.framework. If you have, then make sure the properties of that reference have the copy local property set to true.

    0 讨论(0)
  • 2021-02-02 13:03

    I had the same problem, and I had installed using NUnit-2.4.8-net-2.0.msi. Expanding on the "add to the GAC" comment, here's what I did:

    • Open your "Visual Studio command prompt (generally: make sure gacutil is in your path) and: cd "C:\Program Files\NUnit 2.4.8\bin"

    • Unregister your NUnit entries from the GAC. You can do this by finding the NUnit entries registered in the GAC:

      gacutil /l | find /i "nunit" > temp.bat && notepad temp.bat
      
    • Prepend the nunit.core and nunit.framework lines with "gacutil /uf", i.e.:

      gacutil /uf nunit.core,Version=2.4.2.0,Culture=neutral,PublicKeyToken=96d09a1eb7f44a77
      
      gacutil /uf  nunit.framework,Version=2.4.2.0,Culture=neutral,PublicKeyToken=96d09a1eb7f44a77
      
    • Run your .bat file to remove them: temp.bat

    • Register the NUnit DLL files you need:

      gacutil /i nunit.core.dll
      
      gacutil /i nunit.framework.dll
      
    0 讨论(0)
  • 2021-02-02 13:04

    I got this error message today when I tried to add a new test assembly to an existing NUnit test project. It seems that my test projects had multiple path references to identical nunit.framework.dll assemblies.

    If you have more than one test assembly in your NUnit project, you may want to verify the Path property of the nunit.framework reference in your test projects. Once I made them match, the error message went away.

    0 讨论(0)
提交回复
热议问题