IronPython.net documentation says the MSIL in the assembly isn’t CLS-compliant, but is there a workaround?
IronPython.net documentation says the MSIL in the assembly isn’t CLS-compliant, but is there a
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
IronPython.net documentation says the MSIL in the assembly isn’t CLS-compliant, but is there a workaround?
This was partly a motivation for adding the
dynamictype to C# 4.0. The biggest problem is that IronPython declarations doesn’t include type information, which makes it difficult to use it from C#. Thedynamickeyword adds support for such dynamically typed objects to C# 4.0. See for example:Calling functions/objects from C# 3.0 is a bit more annoying, but it is still possible. You’ll just have to write something like
foo.Invoke("Bar", 42)instead of just writingfoo.Bar(42).