We're planning on using mono embedded in our application, however, since arbitrary users might write code for it we'd need to limit access to certain things, like FS IO, memory allocation and perhaps even network IO.
Does mono have provision for limiting such stuff? Is it simply a matter of limiting which class libraries are available for the mono run-time? Also, is there a way in mono to load an assembly (for execution) from memory (f.i. have the assembly stored in a database) ? TIA /Rob -- View this message in context: http://www.nabble.com/Limiting-access-in-embedded-mono-tp22615263p22615263.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
