Was this following bug submitted into bugzilla; I just ran into the
same one?:
[snip]
Wed, 20 Oct 2004
I fixed in my copy by changing "SharpAssembly " to
"MonoDevelop.SharpAssembly.Assembly.SharpAssembly " in the afflicted
files. Obviously this shouldn't happen because they're using
MonoDevelop.SharpAssembly.Assembly already and referencing the correct
assembly dll. But it's a workaround for now.
Thanks.
-Abe
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
