Following the code example from this website, I created a windows console application that creates a mapped memory file:
using (var file = MemoryMapp
Add "Global\\" prefix to the mapName. That is the only way it worked for me. When we try to access shared memory created in the first process it runs in a different security context and shared memory objects are not visible unless they are created in the global namespace.
This is the code that worked for me. I used CreateOrOpen in a WinForm application and I used OpenExisting in an IIS process:
mSec = new MemoryMappedFileSecurity();
mSec.AddAccessRule(new AccessRule<MemoryMappedFileRights>(new SecurityIdentifier(WellKnownSidType.WorldSid, null), MemoryMappedFileRights.FullControl, AccessControlType.Allow));
mmf = MemoryMappedFile.CreateOrOpen("Global\\\MmfName", 100, MemoryMappedFileAccess.ReadWrite, MemoryMappedFileOptions.None, mSec, HandleInheritability.Inheritable);
mmf = MemoryMappedFile.OpenExisting("Global\\\MmfName");
If Inter Process Communication (IPC) is what you are trying to achieve, you could use WCF with a Named Pipe Binding. You gain a lot of simplicity at the cost of some performance.
For non physical file, there are two cases,
You will have to use http://msdn.microsoft.com/en-us/library/dd267529(v=vs.110).aspx this constructor with following security.
MemoryMappedFileSecurity mSec = new MemoryMappedFileSecurity ();
mSec.AddAccessRule(new AccessRule<MemoryMappedFileRights>(new SecurityIdentifier(WellKnownSidType.WorldSid, null),
MemoryMappedFileRights .FullControl, AccessControlType.Allow));
And then try to access it from IIS with same security.