[Mono-dev] Warnings version conflict mono 2.10 xbuild

Bob Claerhout bob_claerhout at hotmail.com
Thu Aug 11 03:52:28 EDT 2011

I'm currently testing this. There are several libraries I did not made
myself, so some search work needs to be done to recompile these libraries.
I'll come back to you later.

-----Original Message-----
From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of "Konrad M.
Sent: woensdag 10 augustus 2011 16:22
To: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] Warnings version conflict mono 2.10 xbuild

It happened to me when I had references to libraries compiled against
3.5 (which in turn referenced System etc.) in an assembly compiled against
4.0 (which referenced System too). In my case I could just recompile those
libraries to 4.0.

> Hi all,
> I'm developing on windows in Visual Studio 2010. However, we made a 
> build
> server(linux) that builds under mono (version 2.10 with xbuild). When 
> I build on in VS, I don't receive any warnings. However, when building 
> on linux i have 72 warnings of which the most of them are reference 
> conflicts
> like:
> /opt/mono-2.10/lib/mono/4.0/Microsoft.Common.targets:  warning : Found 
> a conflict between : 'System.Core, Version=, Culture=neutral, 
> PublicKeyToken=b77a5c561934e089' and 'System.Core, Version=, 
> Culture=neutral, PublicKeyToken=b77a5c561934e089'. Using 'System.Core, 
> Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089'
> reference.
> I'm building in .Net 4.0 and, as you can see, this is not an error but 
> a warning, so building the project succeeds but with a huge ammount of 
> warnings. Is there a chance this might be solvable such that these 
> warnings don't show up cause I do prefer no warnings at all.

Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list