I want to be able to compile and execute untrusted code at runtime
from within a managed (C#) application. I have accomplished this in
.NET by compiling the code to an assembly on disk, creating a new
AppDomain with a limited permission set, and loading the compiled
assembly into that domain.
Fantastic news! No doubt the leaders of the Mono project over the last
decade-plus have had a huge impact on making this happen, both directly and
indirectly. Thank you (all) for all you have done to get us to this point.
On Nov 12, 2014, at 12:12 PM, Johnnie Odom jo...@escambia.k12.fl.us
It is good to show that you have tested your code; it would be even better
to add tests to the Mono test suite to serve as a regression test.
Also, I could be wrong about this, but I think there is a potential problem
lurking in the new thread_priority field in _MonoInternalThread. It is
declared
Eric Lippert has a good write up about this behavior:
http://blogs.msdn.com/b/ericlippert/archive/2009/03/19/representation-and-identity.aspx
On Oct 24, 2014, at 5:28 PM, Miguel de Icaza mig...@xamarin.com wrote:
Hello,
What happens is this. The value returned from ExecuteScalar is
I'm with you. I have been quite disheartened by the state of CI (or lack
thereof) for Mono, and especially the seemingly constantly broken state of the
Windows build. I haven't wanted to put much effort into fixing the build
because there hasn't seemed to be much of a commitment to keeping it
Long term, the ideal situation is one where we can give more people commit
rights, and review rights. But until we have developed the skills in the
community that are needed, we will continue with the current setup.
This seems to be a chicken-and-egg problem. We need to christen more
reviewers
