Re: [Mono-dev] [PATCH] Source list per profile

2005-08-19 Thread Raja R Harinath
Hi, Yaacov Akiba Slama [EMAIL PROTECTED] writes: [snip] The problem with separate source files per profile is the redundancy : when someone adds a file he needs to add it to several .sources. One way to handle with this problem is to add an include feature in the .sources files. But the price

Re: [Mono-dev] ad Error Building

2005-08-19 Thread Tomas Kalibera
Hi, Are you building mono from the tarball or svn and where are you trying to install to? For the svn version (and IIRC, the tarball as well), it should be ./autogen.sh [options] make su make install I'm building from the tarball, there is no autogen.sh there. What I've been doing for a

[Mono-dev] [PATCH] ToolboxItem icon loading

2005-08-19 Thread Michael Hutchinson
Fairly simple. Also a trivial fix to CreateComponentsCore to maintain compatibility with .NET. I've tested it works with some icons I whipped up for the Web Controls in System.Web.dll, but I'd like to make them a bit prettier before offering them too. Any objections to me committing this?

Re: [Mono-dev] corlib version and #if symbol questions

2005-08-19 Thread Sebastien Pouliot
On Thu, 2005-18-08 at 22:17 +0200, Kornél Pál wrote: Thanks for the information. The patch is now in SVN. I've noticed. Sadly r48519 resulted in 31 regressions in the default profile (NET_1_0) and a little more in the NET_2_0 profile. Please do run the unit tests _and_ ensure that no

[Mono-dev] [PATCH] Default value fixes for WebControl, + UnitConverter infinite loop fix

2005-08-19 Thread Michael Hutchinson
Some corrected default values for the properties of System.Web.UI.WebControls.WebControl. There's also a fix for a potential infinite loop in UnitConverter that occurs when converting to/from non-string types. Could someone review this, and if ther are no objections I'll commit it. On a related

Re: [Mono-dev] [Patch] AssemblyName ctor

2005-08-19 Thread Ben Maurer
Hey, The patch attached implements the new AssemblyName ctor without using internal calls. Could anybody review it? +int GetCharNumericValue (char c) +{ +if (c = (char)0x30 c = (char)0x3B) +return c -

[Mono-dev] System.DirectoryServices and LdapReferralException

2005-08-19 Thread JD Conley
I'm trying to connect up to an Active Directory and run a search and I get a LdapReferralException. For example, I am running a query on the host adserver.coversant.net and while iterating through search results I get a referral exception for

Re: [Mono-dev] Bug with XML Serialization

2005-08-19 Thread knocte
Lluis Sanchez escribió: Can you please file a bug report in bugzilla.ximian.com, and attach a self contained test application that can be used to reproduce the problem? Thanks. Thanks for your answer Lluis. URL of the bug is (I have attached a small testcase):

Re: [Mono-dev] [Patch] AssemblyName ctor

2005-08-19 Thread Carlos Alberto Cortez
Hello again, comments below: + if (String.Compare (parts [i], 0, Version=, 0, 8, true, CultureInfo.InvariantCulture) == 0) This is most likely incorrect and needs to use an ordinal comparison, no InvariantCulture (used more than one time) I'm not sure that's correct. I tested in .Net

[Mono-dev] Need help with signal handlers.

2005-08-19 Thread Mike Hull
Hello, I'm trying to pass signals received with signal.h into managed code. After I mono_runtime_exec_managed_code I can not receive signals using signal(sig,signal_handler). If I don't mono_runtime_exec_managed_code I receive the signals just fine. Currently I'm registering the signal

Re: [Mono-dev] [Patch] AssemblyName ctor

2005-08-19 Thread Kornél Pál
Look at this one: http://msdn2.microsoft.com/library/k13t5kxe(en-us,vs.80).aspx This is ordinal and case-insensitive all in one. It requires .NET 2.0 but the constructor is 2.0-only so this is not a problem. String.Compare with ignore case matches a lot of cases that are considered equal for

[Mono-dev] [Patch] AssemblyName ctor (fixed)

2005-08-19 Thread Carlos Alberto Cortez
Hey, The attached patch contains the latest suggestions of both Kornel and Ben. Maybe the only thing to be noted is that I kept the hexadecimal notation when comparing chars, since the same is used in Char.GetNumericalValue (). New tests are also attached, and run fine under .Net 2.0 Carlos.