I had the same problem and found that it's just a bug in last release.
You can download previous version .23 from the site and it's signed.
Alex
On 6/21/06,
Morten Mertner <[EMAIL PROTECTED]> wrote:
Hi Marc,
> What I do (and I think this is pretty typical) is have a separate unit
> testing project, which has a reference to both the project I'm trying
> to test, and to the MbUnit DLL.
I've seen people using conditionals like "#if TEST" to encapsulate the
test code, mainly because this allows you to access and test internal
methods as well.
Afaik there is no downside to signing the assembly, in which case there
is little reason not to.
Yours,
Morten
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/MbUnitUser
-~----------~----~----~----~------~----~------~--~---
- MbUnit Strong named MbUnit assembly Evan
- MbUnit Re: Strong named MbUnit assembly Marc
- MbUnit Re: Strong named MbUnit assembly Morten Mertner
- MbUnit Re: Strong named MbUnit assembly Alex Bronepolsky
