Windows 8 Integration: Difference between revisions

Line 201: Line 201:
(VirtualAlloc / HeapAlloc and friends)
(VirtualAlloc / HeapAlloc and friends)


<b>Memory execution</b> - Although Virtual* apis do not pass the stand-alone validation test, we have been successful in allocating memory using CreateFileMapping/MapViewOfFileEx. Based on comments by ms employees [1,2] however, it appears applications that attempt to do this will not pass Windows Store certification regardless.
<b>Memory execution</b> - Virtual* / Heap* apis are necessary for allocating executable memory (JIT). We have been successful in allocating memory using CreateFileMapping/MapViewOfFileEx, but based on comments by ms employees [1,2] it appears applications that attempt to do this will not pass Windows Store certification.


<b>Shared memory</b> - While it appears DuplicateHandle is available and passes validation, and memory can be allocated with CreateFileMapping, without process creation & pipes this is of little use.
<b>Shared memory</b> - While it appears DuplicateHandle is available and passes validation, without an approved method of allocating shared memory, process creation and pipes for communication memory can not be shared between processes.


=== Pipes ===
=== Pipes ===
Confirmed users
1,982

edits