So if I have a build server which compiles mono from source using the prefix
/test/dir then when I deploy my application and mono as a tarzip file with
the following contents:
myapp.exe
bin/mono
lib/mono/4.0/mscorlib.dll
lib/mono/gac/System/4.0.0.0__b77a5c561934e089/System.dll
etc/mono/config
etc/
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 1
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 bundl
I am building mono from source using a non-standard prefix. I then am
manually bundling the pieces of mono that I need (not using mkbundle) like
the mono executable, mscorlib, and the class libraries. When I deploy my
application with the bundled mono to a test linux box it works if I am
targetin
