I performed only a partial test, since there are some references used in
certain classes, which I cannot resolve. However, it appears to work with 2.5.8
and all addins show up as enabled. I suspect that the issue is related to how
you are installing
the addin.
Problems like this should be directed to our nunit-discuss forum, where
they are more likely to get quick attention. Use of the bug tracker
should be limited to items that are clearly bugs.
** Tags removed: confirm
** Changed in: nunitv2
Status: New => Invalid
--
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: Invalid
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.
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
