Stefan Bodewig wrote:
Actually, the file:// protocol turns out to be best of all for Windows,
And not only there, it would be the cleanest solution in either case.
this is now an option.
So maybe we should add a way to run that. This leads to a choice of runtimes of more than just net/mono but
ms mono ms-on-mono
which looks like the beginnings of an enum to me.
Absolutely. I've always considered my isMono flags a hack that completely falls down as soon as you want to use Rotor or DotGNU or whatever. That's why I introduced a more flexible approach in the dotnet sandbox area.
I've just patched dotnet.
do we need a <mono> task that execs things; runs them direct on windows, but relays through mono if you ask?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
