From: Ben Maurer
On Fri, 2005-06-17 at 00:29 +0200, Andreas Nahr wrote:
ResourceManager would need to construct a hashtable using more that
500.000
function calls (resulting in a high number of million or even billion
operations) consuming about 1-2MB of ADDITIONAL RAM (additional to the
Ooops, fixed :-)
On Thu, 2005-06-16 at 16:14 +0200, Kamil Skalski wrote:
Dnia roda, 15 czerwca 2005 16:25, napisae:
On Mon, 2005-06-13 at 00:49 +0200, Kamil Skalski wrote:
Attached is the patch moving GenericParameterAttributes to
System.Reflection
Except the case we want to drop the idea of using ResourceManager at all I
think my patch should be reviewed and then committed.
In the case you want to drop ResourceManager I have the following two
questions:
Why are we working on Mono if we think that it unsuitable for it's own needs
as well?
Hi again,
Atsushi Eno wrote:
Hi Joshua,
Yeah, it is likely to happen. Yesterday I found that there is a
problem on namespace handling in DTDValidatingReader and
XmlValidatingReader with kangaroo's help. I think there should
be something similar to what XmlTextReader does. It's not a tiny
fix
I've a simple Web Application which make a call to a webservice method...
(client side)
Since this morning, It crashes when calling the constructor of the
webservice...
the trace is here :
I think it's a problem with XML Serialization!
Hubert
Server error in '/FicheClient' application
First of all lets say this is obviously just my personal optionion:
In the case you want to drop ResourceManager I have the following two
questions:
Why are we working on Mono if we think that it unsuitable for it's own
needs
as well?
I always try to do as much things as possible natively
Hi,
I'm still working on Master Pages (thanks to Lluis), but now I face
another problem : I cannot nest master pages.
Usually this is done by adding a master attribute to the child master
definition tag.
%@ Master Language=C# Master=~/MyMainMaster.master %
but when i try to access a content
Can you please file a bug report in bugzilla.ximian.com for this? and
please attach the code of the web service that fails (if possible) or
the wsdl document?
Thanks,
Lluis.
El dv 17 de 06 del 2005 a les 11:27 +0200, en/na Hubert FONGARNAND va
escriure:
I've a simple Web Application which make
From: Andreas Nahr
I think the question which needs to be answered first is: Does it really
make sense to translate all errormessages at all? Would we even be able to
maintain these for a number of languages and which gain would we get from
it.
If someone wants to traslate them he can do it. I
Atsushi Eno wrote:
And now it should be fixed (at r46122). I removed some nastly
default xmlns* attributes handling.
Much appreciated. (Tho I haven't tested it.)
--
- Joshua Tauberer
http://taubz.for.net
** Nothing Unreal Exists **
___
Hi Andrew,
*regarding subj*, I think we should not mix different things:
- Wellformedness in XmlTextReader
- Validity in XmlValidatingReader
- How XmlEntity/XmlEntityReference behaves
Since the standalone test should basically target validity in
XmlReader, the way that
What is the exact exception thrown - and where does the stack trace
say it originated - it does indeed sound like a certmgr thing, but
more information would help.
Martin
On 6/17/05, Jeff Tickle [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not sure if it's a bug or
Hi,
When using a GridView with a ButtonField column as below:
asp:gridview id=MyGridView runat=server AutoGenerateColumns=false
columns
asp:ButtonField
CommandName=Select
HeaderText=Code
DataTextField=CodeAction
/
/columns
Hi, Atsushi.
Just to set things straight. The patch was rejected since it was incomplete
caused regressions and you didn't like the approach. The lack of concrete
test case at the time that motivated the patch prevented us from continuing
the discussion at that time. Now that the lost test was
Hi Eyal,
Just to set things straight. The patch was rejected since it was incomplete
caused regressions and you didn't like the approach. The lack of concrete
test case at the time that motivated the patch prevented us from continuing
the discussion at that time. Now that the lost test was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, here's the exception:
System.Net.WebException: Not connected --- System.IO.IOException: The
authentication or decryption has failed.
in 0x001e1
Mono.Security.Protocol.Tls.SslClientStream:NegotiateHandshake ()
in (wrapper
And now, here I am at work without my GPG key. Oh well.
I did some more bug searching now that I've learned a bit more about
what's going on here through IRC and such. Turns out certificate trust
seems to be a problem in mono. I'll investigate it more, but for now,
the workaround is to simply
Hi,
Could someone tell me why do I get cygmono-1.dll and cygMonoPosixHelper.dll
when I compile Mono while in the binary distribution for Windows there are
mono-1.dll and MonoPosixHelper.dll?
Thanks.
Kornl
___
Mono-devel-list mailing list
Hi,
Its an artifact of using libtool for creating the dlls. libtool
thinks we want to
start all our dlls with 'cyg' and can't be convinced otherwise.
Zoltan
On 6/17/05, Kornl Pl [EMAIL PROTECTED] wrote:
Hi,
Could someone tell me why
Its an artifact of using libtool for creating the dlls. libtool
thinks we want to
start all our dlls with 'cyg' and can't be convinced otherwise.
Zoltan
And how are the dlls built for the installer that they don't start with
'cyg'?
Kornl
Hi,
No idea. They are probably simply renamed.
Zoltan
On 6/17/05, Kornl Pl [EMAIL PROTECTED] wrote:
Its an artifact of using libtool for creating the dlls. libtool
thinks we want to
start all our dlls with 'cyg' and can't be convinced otherwise.
21 matches
Mail list logo
