Hello,
I have to thank Microsoft to open-source the .Net library allowing me to
read their code to get to the bottom of Microsoft's treatment (even I have
already asserted the value at runtime) of default values for the
System.Diagnostics.DefaultTraceListener. For those interested in reading
this
(This is my personal opinion, I'm not a collaborator) This is also a
question that is better for the dev list.
My personal opinion is that if it's a verbatim port from the
referencesource on github, that you shouldn't be precluded from
contributing.
Anything beyond that would be questionable I
On Nov 21, 2014, at 7:25 PM, MarLOne infoseeker...@gmail.com wrote:
It will be good if these classes and assemblies from Microsoft open-sources
are incorporated verbatim into Mono to replace its inconsistent code.
This will not be possible, for (at least) three reasons:
1. That code is also
On 09/03/14 06:28, MarLOne wrote:
Hi all,
I have found out the run time discrepancy of Debug.Assert() in CLR and in
Mono. The answer literally is in front of our eyes.
The difference is in this property:
System.Diagnostics.DefaultTraceListener.AssertUiEnabled.
In *CLR* the default
Oops..
Anyway.. The reason why it is false by default is that there is no
trace listener enabled by default.
You can enable it in several ways.
1. export MONO_TRACE_LISTENER=Console.Error
2. Adding one.
var tl = new System.Diagnostics.ConsoleTraceListener();
Hi all,
I have found out the run time discrepancy of Debug.Assert() in CLR and in
Mono. The answer literally is in front of our eyes.
The difference is in this property:
System.Diagnostics.DefaultTraceListener.AssertUiEnabled.
In *CLR* the default value is *true* but in *Mono* the default value
Hi,
Why is Debug.Assert(false) not terminating/aborting not a bug and has not
been fixed since it was first raised in 2006?
I am using MD4.2.2 in Mint-15 and it still fails to behave correctly out of
the box and wasting people's effort. Sure, one can register tracelistener
into the chain. But if
From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of MarLOne
Why is Debug.Assert(false) not terminating/aborting not a bug and has not
been fixed since it was first raised in 2006?
This post belongs on the dev list. It would be best if you go
Before getting familiar with mono you should first get familiar with how
opensource development works. Read about talk is cheap, easier said
than done, etc. (that is, if you think Mono should behave in some way,
go ahead and try to make it so).
On 07/03/14 15:17, MarLOne wrote:
Hi,
Why is
