I made the whole build process work (it wasn't as bad as anticipated ;-). I found out that I made a cyclic dependency: some classes (AsymmetricAlgorithm, DSA, RSA) requires XmlDocument. And still the problem didn't show up until I tried a "make clean" (else it would just use the one present in System.Xml.Dll). These classes have been excluded from the build process (probably just because of this) but I wasn't aware of it. So this is the reason for the class library is compiling just fine.
However the problem is that the test assembly are (or were) referencing these classes (again thanks for removing the offending code). Question: What's done elsewhere for those kind of cyclic dependency ? > > The recently submitted unit tests for Crypto are producing lot of > > errors. Seems to be at least one error per test file or so. Note that I didn't have any other error (for the other classes) - so I will still be needing the logs in order to correct any remaining problems. Sebastien Pouliot Security Architect, Motus Technologies, http://www.motus.com/ work: [EMAIL PROTECTED] home: [EMAIL PROTECTED] _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
