Sounds like you need to solve the deployment of mono for your target first.
Expecting the gac to work in the situations you describe isn't going to work. If you are distributing your program internally to your company or home stuff you can try the static linking option to mkbundle On 3 Jul 2013 17:46, "markcoburnwa" <mcob...@globalscape.com> wrote: > I found that if I copy lib/mono/2.0/mscorlib in addition to > lib/mono/4.0/mscorlib then I am able to avoid the complaints about not > finding mscorlib and am able to use C# 4.0 features. Unfortunately, this > workaround does not function on the one system where I am using mkbundle > because it only bundles lib/mono/4.0/mscorlib. > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/mscorlib-dll-was-not-found-or-could-not-be-located-tp4660087p4660096.html > Sent from the Mono - General mailing list archive at Nabble.com. > _______________________________________________ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list >
_______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
