Closed jochenjonc closed 13 years ago
Jochen,
We ran into the same thing, and it appears to work if fit.dll is among your added assemblies in <ApplicationUnderTest>.
This seems like a bug to me, that's come through because fitSharp's own tests are testing fit.dll, and so it's naturally included the assemblies. Users would probably expect fit.dll types to be natively available. At least we did.
Hope that helps,
Indeed that worked. I'll keep the case open because I think it's a bug.
Glad it helped.
Do you know if there's a mailing list or similar support forum for fitSharp? I'm new to it, and haven't found a community...
Thanks,
No I don't, you have the fitnesse Yahoo group, but for questions specific to fitsharp there is no group.
Maybe it's time to get all information in one place and start a community.
Jochen
Thanks!
Not sure, there's probably some benefits to a shared community and others to a separate community. But if discussion delves into implementation details like this one, a dedicated community might cause less disruption for regular FitNesse subscribers.
This comment box isn't ideal for discussion ;-)
Yes, it's a bug and the workaround is to include fit.dll in the assemblies.
auto load fit.dll
Hi,
I have a problem with the latest version of FitSharp. When I start the runner I get an error if the SuiteConfiguration file contains Fit.Operators.
...
I'm I doing something wrong, or is this a bug?
Jochen