On Jul 13, 2012, at 11:23 AM, Matthias D. matth...@googlemail.com wrote:
I'm porting a .net application to mono and I noticed a small inconsistency in
System.Diagnostics.DefaultTraceListener. In .net this class has a public
constructor and in mono it has only a private one (none in the source
On Jul 14, 2012, at 6:26 AM, Matthias D. matth...@googlemail.com wrote:
Ok I figured it out, the problem was using the answer from this:
http://stackoverflow.com/questions/1769772/reading-tracelistener-initializedata-property-from-config-net-1-1
and in mono there is no field called
On Jul 13, 2012, at 11:23 AM, Matthias D. matth...@googlemail.com wrote:
I'm porting a .net application to mono and I noticed a small inconsistency in
System.Diagnostics.DefaultTraceListener. In .net this class has a public
constructor and in mono it has only a private one (none in the source
On Jul 14, 2012, at 6:26 AM, Matthias D. matth...@googlemail.com wrote:
Ok I figured it out, the problem was using the answer from this:
http://stackoverflow.com/questions/1769772/reading-tracelistener-initializedata-property-from-config-net-1-1
and in mono there is no field called
Hey,
Ok I figured it out, the problem was using the answer from this:
http://stackoverflow.com/questions/1769772/reading-tracelistener-initializedata-property-from-config-net-1-1
and in mono there is no field called initializeData. I did found another
workaround though.
@Rob, thanks for the quick
Hey,
I'm porting a .net application to mono and I noticed a small inconsistency
in System.Diagnostics.DefaultTraceListener. In .net this class has a public
constructor and in mono it has only a private one (none in the source
code). Its nothing critical for me (as the workaround was simple) just
If you don't want this forgotten, i'd suggest filing a bug report in
addition to reporting it here --
http://www.mono-project.com/Bugs
If it doesn't have a constructor in mono implemented it may be an
incomplete implementation in which case it may be a bigger project than
just creating a
