On Wed, Feb 8, 2012 at 8:00 PM, Alan alan.mcgov...@gmail.com wrote:
These attributes are only generated as part of the moonlight build. There
is no way to create them unless you modify the Makefiles to allow them to
be generated in an alternate way. This is also not something which we
should
Hi Alan,
As you said I am already embedding mono in my framework, enabling core-clr
and also registering all function callbacks to determine platform code.
Here my requirements are to restrict access to FileIO and system calls. I
am able to achieve a part of it by enabling core-clr but not the
The best documentation for this is:
http://www.mono-project.com/CoreClrHowTo#Profiles and the other pages it
links to.
Alan
On 9 February 2012 06:11, Anshya Aggarwal anshya.aggar...@gmail.com wrote:
Hi Alan,
As you said I am already embedding mono in my framework, enabling core-clr
and also
Hi All,
I am building the mono with --with-moonlight=no, as per my knowledge mono
dont have core-clr security attributes(safecritical/critical/transparent)
enabled by default in mscorlib.dll or system.dll etc if moonlight flag is
not enabled at compilation. So, I want to know that is there a way
These attributes are only generated as part of the moonlight build. There
is no way to create them unless you modify the Makefiles to allow them to
be generated in an alternate way. This is also not something which we
should enable by default because it increases build time significantly and
is
