Hi, all of you.
I've finally found a solution to this problem by myself. Since probably
many people will stumble upon this, I think it is better to somehow
register it.
The problem seems to be in System.Drawing. When you try to launch an
application using WinForms, it crashes with:
==
Unhandled
Thank you too, etienne, for testing and commiting bug fixes.
On Tue, 2014-04-08 at 21:33 +0200, etienne.champet...@free.fr wrote:
Hi
This thread is named FastCGI performance, but much more important than
performance is stablility, ie don't explode (10Gb memory usage :)).
I want to
Marcello,
I'll try to find a way to remove ASP.NET dependency, in this case you'll
be able to reuse communication part of the HyperFastCgi and provide an
additional way to write FastCgi http servers.
On Tue, 2014-04-08 at 18:01 -0300, Marcelo Zabani wrote:
xplicit, perhaps we could concentrate
Hi,
I became involved in a conversation today on LinkedIn in which a
commentator was telling me Mono is dead, due to contractual
constraints imposed on Xamarin by the legal owners of Mono, Attachmate.
A snippet of the ensuing conversation follows,
In July 2011, however, Novell - now a
I like this. If it provides the ability to easy change one listener to other
and also ability to change HTTP servers it'll be awesome. By the way it also
should provide the ability to run current ASP.NET server otherwise people
could not migrate their web application to Linux platform. ASP.NET
Facts tells a lot more gossip.
Mono has been steadily growing since Xamarin started. The size of the core
team working on mono have expanded and the number of external contributors
is growing even faster.
On Wed, Apr 9, 2014 at 3:36 PM, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:
On 09/04/2014 22:00, Robert Jordan
wrote:
Were
you living under a stone the past couple of years? :D
Just trying to understand the realities Robert :-D
You're
mixing up Mono MonoTouch like they were the same
On 09.04.2014 23:17, Alex J Lennon wrote:
A key component of what I was told toay is that Xamarin are unable to
work on Mono due to contractual obligations to Attachmate. As a
result they are (I am told) abandoning Mono and doing something
else which is the (presumably) VM underneath the
On 09/04/2014 22:27, Chris Tacke wrote:
If
you take a look at the live repository for Mono, you can see
that Xamarin employees regularly update the source code
(there are changes from 2 hours
If you take a look at the live repository for Mono, you can see that Xamarin
employees regularly update the source code (there are changes from 2 hours
ago). That places the statement that Xamarin are unable to work on Mono
clearly into the FUD column.
Mono is actively being fixed and
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Alex J Lennon
Many thanks for bringing clarity to this for me Chris. As we're in a public
forum I hope hope you won't mind me referencing this discussion now and in
future when it
Just checking on this, as I didn’t really get any feedback. Do I need to open
a defect to have this pull request merged or is there something else I need to
do so the maintainer of io.c notices it?
On Apr 9, 2014, at 12:19 AM, David Curylo cury...@asme.org wrote:
I came across the behavior
On 08.04.2014 11:40, Baltasar García Perez-Schofield wrote:
Hi, there.
While trying to execute my app using WinForms (created with Mono and
MonoDevelop, and working just right up until now), I have stumbled with
this, using Windows 7:
==
Unhandled exception:
...snip...
missing
Hi,
I have a very simple SQLite database class which I'm using
System.Reflection to serialise and use within my DBManager class.
My class looks like this (it's a test case to try and get things working
before I integrate it)
public class dbclass
{
[PrimaryKey]
public string Id {
How about checking whether the IgnoreAttribute is applied to
the property?
for (int i = 0; i properties.Length - 1; i++) {
// ignore props marked with [Ignore]
if (properties[i].GetCustomAttributes(typeof(IgnoreAttribute),
false).Length 0)
next;
}
Robert
On
Hey folks,
Are there any APIs or any simple ways to get information from the GC like
minor/major generation sizes, # of objects allocated, etc.. programatically?
If not programatically then a way from the command line to probe the GC
would be great. I know there is dtrace but I am looking for
Hi Robert,
How about checking whether the IgnoreAttribute is applied to
the property?
for (int i = 0; i properties.Length - 1; i++) {
// ignore props marked with [Ignore]
if (properties[i].GetCustomAttributes(typeof(IgnoreAttribute),
false).Length 0)
next;
}
Perfect. Why
Hi, all of you.
I've finally found a solution to this problem by myself. Since probably
many people will stumble upon this, I think it is better to somehow
register it.
The problem seems to be in System.Drawing. When you try to launch an
application using WinForms, it crashes with:
==
Unhandled
Yes that looks like what I need. Also seeing which options have been set
would be nice. I have set some environment variables for MONO_GC_PARAMS but
its difficult to know whether they are being respected.
--
View this message in context:
Hi,
An yep, bugs happen. However, the bug was found in 11/2012 (mono 3.0.1),
and bug 14586, a duplicate of this bug, was (re-)found in 09/2013.
Currently, in 4/2014 (mono-3.2.3), the bug has not still been solved,
while the fix seems just to add an os=!windows attribute to those
lines. I
20 matches
Mail list logo
