Question

I’ve ran into a bit of a stupid problem today:

In my project I have to use a library (that I can’t replace), he problem is that I’m using MemoryStream instead of frequently saving to the HDD (because there are many files, and they are small in size, so it’s perfect for MemoryStream). The problem is that the library API is built around filesystem access – and one of the functions accepts only direct path to file.

How can I still send a string (path) to the method, which makes a new FileStream without actually touch the hard-drive?

For example “\MEMORY\myfile.bin”?

Answer 1

Well – that’s thought.
Basically, you have three possible solutions:

1. You can use a reflector to modify the library given.
2. You can inspect the appropriate method, and then, by using some reflection magic you might be able to modify the object at runtime (very un-recommended)
3. You can play around with system calls and API – and by going into low-level ring0 assembly modify kernal.dll to referrer I/O queries from your path to the memory. (maybe that’s possible without ring0 access – I am not sure).

Obviously, the most recommended is to use a reflector to modify the library given. otherwise, I can’t see a solution for you.

In respond to the first comment, you can:
use RAMDrive (a program which allocates small chunks of the system memory and show it as partition)