> we need this fix pulled into the codebase ASAP.
Well ok! Listen, I appreciate your concern. But... It seems like you fixed the problem for yourself. Why does it need to be in the codebase "ASAP"? I don't understand the urgency. Can you explain.
> We're happy to provide some Mono support and compliment your team on this :)
I see this a lot. Comments like "Hi everyone!" OR "Hello, guys!" or some reference to "your team." Look, there's no "team". There's just me. One guy. Just one. So... When you say stuff like "where's the
response?!?!" it's not like there are 7 people volunteering to respond to these questions. It'd be nice if *someone besides me* contributed answers once in a while on this forum. Or contributed in a way that did not produce more demands for my
time. Regardless, I answer the ones I can, and I answer when I can.
If you are interesting in contributing, contact me and say so. I will not let just anyone onto the project. I'll need to evaluate your work. I haven;t seen anyone submit patches via the codeplex system. In other words: so far I don't have any
way to evaluate competency or goodwill. Obviously, I will not add contributors if I am not confident in their competency.
Getting back to the core issue, regarding the use of Path.SeparatorChar in the method in question, the fix proposed here sounds reasonable. Problem is, I don't have a mono/linux workstation, I don't have a VM, and I don't have the ability to test the fix
you are proposing. I also will not expand my testing effort beyond the existing work I'm doing. I am spending enough time on this; I will not do more. It may be a simple matter of installing Ubuntu and Mono and then running a test suite,
but. . . I am not willing to do that.
I'm glad you guys are using the library on Mono. Really. I'm pleased to hear it. I hope it's useful. I'll do what I can to make that easy. To encourage it. I can insert mon-related fixes into the codebase that you, or anyone in the community,
proposes. But I have no Mono tests for them, and since you already have the fix, I don't see the benefit to you, if I insert the fix in a changeset here, "ASAP".
I'll be interested to hear your feedback.