nunit-core team mailing list archive

[Matt Smith <mtscout6@xxxxxxxxx>]

Public bug reported:

I have some addins that have been working on Version 2.4.7. In an effor
to upgrade our system to 2.5.3 I set out to upgrade our addins. I made
sure to reference to new 2.5.3 assembly references and changed the
implemented interfaces where appropriate. That all seemed to work fine,
however when I added them to the addins folder in the bin directory I
can see them in the addins dialog and they all say error. The message
is: Unable to locate
IdahoTech.Testing.NUnitExtensions.TestForTestCompleteAddin,
IdahoTech.Testing.NUnitExtensions, Version=1.0.0.27259, Culture=neutral,
PublicKeyToken=null Type. I went over the source code the best I could
to see what was causing the issue. I have noted that my assembly is not
even loaded in the current app domain. I tried loading the dll in the
current app domain and I still got the same error. I don't know if this
is necesarrily a bug or if I am not implementing something necessary for
the load.

** Affects: nunitv2
     Importance: Undecided
         Status: New


** Tags: addins

-- 
Addin's don't load
https://bugs.launchpad.net/bugs/519052
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: New

Bug description:
I have some addins that have been working on Version 2.4.7. In an effor to upgrade our system to 2.5.3 I set out to upgrade our addins. I made sure to reference to new 2.5.3 assembly references and changed the implemented interfaces where appropriate. That all seemed to work fine, however when I added them to the addins folder in the bin directory I can see them in the addins dialog and they all say error. The message is: Unable to locate IdahoTech.Testing.NUnitExtensions.TestForTestCompleteAddin, IdahoTech.Testing.NUnitExtensions, Version=1.0.0.27259, Culture=neutral, PublicKeyToken=null Type. I went over the source code the best I could to see what was causing the issue. I have noted that my assembly is not even loaded in the current app domain. I tried loading the dll in the current app domain and I still got the same error. I don't know if this is necesarrily a bug or if I am not implementing something necessary for the load.