As a further addition, this works fine when I build on Windows with Mono
3.4.0.
But not with 3.2.3, which just gives me a different error at runtime about
ExtensionAttribute not being found.
This is way too flaky for my liking - I'm abandoning xbuild and just
building for Mono with msbuild from
I've discovered that mono is using mscorlib from `\lib\mono\4.5`, rather than
`\lib\mono\4.0`.
Now, `xbuild` is in `\lib\mono\4.5`, but my project targets .NET 4.0. Any
ideas as to what is going on here?
--
View this message in context:
On 13/05/14 11:28, cocowalla wrote:
I've discovered that mono is using mscorlib from `\lib\mono\4.5`, rather than
`\lib\mono\4.0`.
Now, `xbuild` is in `\lib\mono\4.5`, but my project targets .NET 4.0. Any
ideas as to what is going on here?
Seems there is a bug in the makefiles. If you ran
The build machine isn't running a trimmed down mono - it's a Windows machine
that uses the official 3.2.3 binaries, which IIRC doesn't give you the
option to leave out 4.5 support.
The machine with the trimmed down mono is a Linux box.
Is there some kind of workaround for Windows so I can build
On 13.05.2014 11:28, cocowalla wrote:
I've discovered that mono is using mscorlib from `\lib\mono\4.5`, rather than
`\lib\mono\4.0`.
Now, `xbuild` is in `\lib\mono\4.5`, but my project targets .NET 4.0. Any
ideas as to what is going on here?
Try to preset a specific runtime version while
I should have said I was using `--runtime=v4.0` when trying to run it.
I tried the 2 difference versions you suggested, but get this for both:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Core, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one
On 13.05.2014 14:56, cocowalla wrote:
I should have said I was using `--runtime=v4.0` when trying to run it.
I tried the 2 difference versions you suggested, but get this for both:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Core, Version=4.0.0.0, Culture=neutral,
I get:
The following assemblies are installed into the GAC:
System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089
Number of items = 1
For completeness, here is the complete command I am using to trim down the
mono build:
CC=gcc -m64 ./autogen.sh --prefix=/opt/mono64
I should add that System.Core does exist in /opt/mono64/lib/mono/4.0
--
View this message in context:
http://mono.1490590.n4.nabble.com/The-assembly-mscorlib-dll-was-not-found-or-could-not-be-loaded-tp4662752p4662770.html
Sent from the Mono - General mailing list archive at Nabble.com.
OK, figured it out. I needed to set MONO_PATH to:
/opt/mono64/lib/mono/4.0:/opt/mono64/lib/mono/3.5:/opt/mono64/lib/mono/2.0:.
So I needed to tell it where to look for libraries; I had (wrongly) assumed
that would be automatic based on the location of the mono executable.
--
View this message
I'm running a trimmed down mono, built without the 4.5 profile using
--with-profile4=yes --with-profile4_5=no.
I have an application that targets .NET 4.0, built using xbuild. When I run
it against my trimmed down mono installation, I get this error:
The assembly mscorlib.dll was not found or
11 matches
Mail list logo