No idea.
On 07/03/2013 05:30 PM, Martin Thwaites wrote:
Is this message not getting through? is it just that no one knows the
answer, can someone just send a simple "No idea" so I know this is
getting through. It's the first time I've used the list.
On Mon, Jul 1, 2013 at 9:49 PM, Martin Thwa
Hello,
I am running into an OutOfMemoryError when running a VS-compiled
assembly (specifically, when calling AllocHGlobal even for very small
amounts of memory) in Mono. The problem does not occur when using the
stock MS runtime. My first thought was to fire up the Mono debugger, but
it a
Is this message not getting through? is it just that no one knows the
answer, can someone just send a simple "No idea" so I know this is getting
through. It's the first time I've used the list.
On Mon, Jul 1, 2013 at 9:49 PM, Martin Thwaites wrote:
> I'm trying to get mono working from source s
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
