Long Files paths

I see that your checkin comment does not seems to be favourable for the BCL..

I also was wanting to use this library to solve the same problems, so would like to here what you are doing, and what the problems area, And whether we (We) should be using pInvoke to solve these problems.

I have found floating around a small library, that mirrors File.Open, File.OpenRead, etc. static methods and implements them using Win32 P/Invoke. After that, all file I/O should be done using these libraries. Also note that some Path.* static methods also
have the limit of 255 chars in the path, so they too should be mirrored to allow full long-path functionality. I use Path.* quite a bit, so this is stopping me to support long paths for now, as I haven't found the time to implement all those functions. Let
me know if long path support is important to you, and if you can dedicate someone to work on this, may be we could collaborate on this one, as one more complete implementation will add a good value to both projects.