[Mono-bugs] [Bug 457065] incorrect system.web.extensions w/ install packages?

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Dec 8 18:38:34 EST 2008


https://bugzilla.novell.com/show_bug.cgi?id=457065

User mhabersack at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=457065#c3





--- Comment #3 from Marek Habersack <mhabersack at novell.com>  2008-12-08 16:38:33 MST ---
(In reply to comment #2 from Mike Morano)
> Hi Marek,
> 
> Thanks for your comments, and indeed, you confirmed what I believed to be true,
> which is that mono moved _away_ from the newtonsoft libraries.
> 
> However, I think my bug is still valid in how the prebuilt binaries are
> created.  The ones I had installed for my opensuse installation _were_
> referencing the newtonsoft library, which I could tell when I ran XSP in trace
> mode, and this is what I believe to be the bug.  As you stated, mono should now
> be using the mono implementation.
There should be no references to the upstream newtonsoft library as it was
never linked to directly. Instead, we had some source files of theirs included
directly in the build.

> I was suggesting that perhaps the binary was built by referencing the .csproj
> files, as that is the only place I could see anything in my checkout from svn
> referencing these newtonsoft related files.  I too do not use VS for building
> anything on mono, so have no patches in that regard.  This is why I built
> everything manually, so that I could run my app w/o the newtonsoft library.
The rpms are built using makefiles, so I'm not sure what kind of bug you are
seeing, frankly.

> 
> Sorry for any confusion, I just want to make sure the right version is getting
> bundled as part of the final build that creates the binaries that everyone is
> downloading and using.
Are you sure you didn't have several versions of sys.web.ext available?

marek


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list