Basically something that's not .NET code. There are security implications (Unmanaged code can be insecure, as it bypasses most of .NET's security features) and potential stability issues.

Think of it as XS for .NET--while you can do anything you want and interface to some external library or other, there's nothing to stop the code from stomping on the world. It also means you'll need the perl component on any machine executing your perl code in the .NET environment, though I think .NET's packaging scheme takes care of fetching that as need be. (I'm not 100% sure of that, thoug)

In reply to Re: Re: Re: ActiveState Perl for .NET by Elian
in thread ActiveState Perl for .NET by BrotherBrett

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.