On Mar 18, 2004, at 8:48 AM, J�lio C�sar K�del G. wrote:
2) In my applications, I use some components made by a company called
ComponentOne (the famous ComponentOne TrueDBGrid). Those libraries are made for
Microsoft .Net Framework, and there is no source code (are proprietary
controls). Mono would run a proprietary control or the control MUST be compiled
in the running system (i.e. Linux or MacOSX). In other words: existing
components for .Net would run in Mono or I must have specific versions to
different plataforms?



It's tricky to gauge how well a component runs under .NET. I have found that many of those companies that have a background in VB6/COM, an ComponentOne is certainly one of those companies, have "'.NET Components" are nothing more that three different things:


1. A Interop wrapper around the already existing COM component
2. A assembly that basically passes calls through to the COM component
3. An assembly that actually unpacks the existing COM component, then runs it.


I have come across all three during my .NET development. So, buyer beware. Just because it says '.NET Component', doesn't mean it's a pure .NET component.

Just a heads up.

-Griffin
_______________________________________________
Mono-list maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to