Sounds good. But you can probably tell what's on my mind... Is it testable?
Steven Boswell II wrote
https://github.com/mono/mono/commit/ecef298bcaf571a3d50e022318b20117f9d0388c
introduced another bug that I found today. Enclosed is the fix.
DataGridViewTextBoxCell was creating a single
On Jun 22, 2012, at 9:35 AM, Rob Wilkens robwilk...@gmail.com wrote:
Do you know where i can find documentation for Mono.Posix?
Documentation is in git:
https://github.com/mono/mono/tree/master/mcs/class/Mono.Posix/Documentation/en
Accessible from the web:
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
Unless you _really_ need a System.Data.Linq-compatible API, I would suggest
giving up. Instead, focus on getting the open-source EF release working on
Mono, and use that instead.
http://entityframework.codeplex.com/
- Jon
On Jul 31, 2012, at 4:06 AM, Sharique uddin Ahmed Farooqui
So ermshiperete gets to check in changes with no unit tests that break stuff,
and I have to submit unit tests to prove I fixed those bugs?
I'm just jealous, is all ;-)
Enclosed is the desired unit test for patch #20.
Any thoughts on checking in patches #18a and #19?
Steven Boswell
