[Mono-dev] mono with CoreCLR: How to add custom assemblies

[chandrakant mishra]

Hello Sebstien,

Thanks for that prompt reply. I had looked at that link earlier but could
not produce a good method to do it. Pardon my superficial knowledge on this
subject. I haven't looked at moonlight code yet. So do you mean that the
moonlight code base contains that part to load an assembly as a platform
code?

Thanks again,
Chan

On Tue, Jan 17, 2012 at 9:34 PM, Sebastien Pouliot <
sebastien.pouliot at gmail.com> wrote:

> Hello Chan,
>
> Have a look at
> http://pages.infinit.net/ctech/20110113-0841.html
>
> it will point you to the related wiki pages on mono-project.com.
>
> Note that the best resource on the subject is the moonlight code base.
>
> Sebastien
>
> On Tue, Jan 17, 2012 at 11:00 AM, chandrakant mishra <
> chandraelxsi at gmail.com> wrote:
>
>> Hi All,
>>
>> I have just started with mono and currently working on enabling security
>> while embedding mono into my platform. I am not using moonlight but want to
>> use its browser security features[CoreCLR] in mono.
>>
>> The problem here is that I have certain custom class libraries [dlls
>> compiled just with mcs without a strongname and version and containing
>> critical p/invoke and unmanaged code] which I want to be a part of platform
>> code. From what I understand, p/invoke and unmanaged code can only exist as
>> critical platform code under CoreCLR. But with what I have tried till now,
>> I have not been able to add my assemblies as platform code. Is there a
>> tutorial on web that could help me with this? Any idea on this will be of
>> much help.
>>
>> Thanks,
>> Chan
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>


-- 

Thanks and regards,

Chandrakant Mishra || Sr. Software Engineer, SISC || Ph: +91-9013463789
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20120117/01db2cb5/attachment.html>