Hi,
I was using with success a web application on Centos with mono 2.4.2
compiled from source.
To try the new version I downloaded the Mono 2.4.3 Virtual machine, I
copied my web application to the new server and it gives an error
cause Crystal Reports dll are missing.
Those dll are
I tried placing crystal libraries inside bin directory and now it
asks for various visual studio (the build is done with visual studio
on MS.NET) libraries that are obviously missing.
What I'm doing wrong?
At 12.09 16/11/2009, APS wrote:
Hi,
I was using with success a web application on
AFAIK, CrystalDecisions.CrystalReports.Engine is only added to an
ASP.NET project if you add a Report to it. If you don't use reports
yank it out of the project.
Mono doesn't implement the report engine that MS sublicensed from
Crystal Decisions (now part of SAP) to distribute with Visual Studio.
I agree with you, I already replaced Crystal but
some legacy module still reference it. I don't
use it on Mono, and I don't distribute it, it's
only referenced in some assembly (and by now I can't remove the reference).
What is strange is that Mono 2.4.2.3 rebuilt from
source on a CentOS
The lengths of strings that are larger than 127 bytes are encoded
incorrectly by the Mono.FastCgi.NameValuePair.WriteLength method: The first
byte must have its high bit set in this case. To confirm, refer to the
implementation of the reverse decoding-logic in the ReadLength method and
see the
On Fri, 2009-11-13 at 12:06 -0500, James P Michels III wrote:
I would like to submit this patch to correct a minor mistake in the
DefaultWatcher.cs source.
The change corrects an instance of unsynchronized access to shared state
and is probably the intent of the original code.
The patch
Instead of adding the changes for MIPS-EL (Loongson) to just the
trunk, is it possible to add them to the 2.4.x branch as well??
Thanks,
Rayson
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Hello,
It is too difficult for us to support that branch for platforms
that were not supported at the time. Until we have a release that
officially supports a platform, we really are not backporting fixes
for older partial ports.
On Nov 16, 2009, at 4:52 PM, Rayson Ho wrote:
