<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Comments for Overview of the VCL for .NET</title>
<link rel="alternate" type="text/plain" href="http://dn.codegear.com/article/29460" title="Overview of the VCL for .NET" />
<link rel="self" type="application/atom+xml" href="http://dn.codegear.com/article/29460/feed" title="Comments for Overview of the VCL for .NET" />
<id>http://dn.codegear.com/article/29460</id>
<updated>2008-08-30T02:47:00-07:00</updated>
<entry>
<title>re: Overview of the VCL for .NET</title>
<author>
<name>Danny Thorpe</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33989</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33989</id>
<updated>2003-01-27T17:08:33-08:00</updated>
<published>2003-01-27T17:08:33-08:00</published>
<summary>re: Overview of the VCL for .NET</summary>
<content>VCL for .NET components should be useable by other .NET development tools.  This is hypothetical at the moment since that part of VCL for .NET has not yet been implemented.Non-visual components will have an easier time with interoperability than visual controls.  Also, some Delphi language features (such as sets) will not be understood by other .NET tools, and will thus be tagged as &quot;non-CLS compliant&quot; by the compielr.  This is fine - C# and VB have non-CLS corners, too.  Example:  CLS excludes unsigned integers from its list of supported types.  Like Delphi for .NET, C# and VB can declare methods with unsigned integer parameters, but these methods may be rejected or ignored by other .NET tools because unsigned ints are non-CLS compliant.A .NET developer using any .NET language tool who wants to write components for use in other .NET tools will need to understand which features of their language/toolset are not useable by other .NET tools and provide equivalents through other methods in the component.  For example, if a Delphi for .NET developer wants to use a Delphi set type as a parameter in a method declaration, he/she should consider providing an equivalent method that does not require Delphi-specific knowledge, perhaps by making that parameter a simple integer parameter.  The same is true for C#, VB, Eiffel, Cobol, and any other .NET language tool.Sharing visual controls between different application frameworks is a bit more complicated, but not impossible.  A worst case would be that controls of one framework would need to be wrapped with host sites that are compatible with the other framework.  That's what ActiveX controls do in Delphi 7.  We might be able to do better than that in .NET thanks to CLR metadata and runtime introspection.BTW, you can already drop existing VCL components and forms into .NET applications using the ActiveX technique - place your VCL component in an ActiveX wrapper, and import the ActiveX control into your .NET application.  It's not elegant, but it works.-Danny</content>
</entry>
<entry>
<title>Overview of the VCL for .NET</title>
<author>
<name>Gintaras Pikelis</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33970</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33970</id>
<updated>2003-01-22T14:44:26-08:00</updated>
<published>2003-01-22T14:44:26-08:00</published>
<summary>Overview of the VCL for .NET</summary>
<content>HiAnd what is the future of VCL.NET components (3rd party) ? Any way to build components that can be used in other .NET tools like VB.NET ? Like we currently have ability to build ActiveX components.thanks</content>
</entry>
<entry>
<title>Overview of the VCL for .NET</title>
<author>
<name>Patrick Foley</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33903</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33903</id>
<updated>2003-01-15T00:15:13-08:00</updated>
<published>2003-01-15T00:15:13-08:00</published>
<summary>Overview of the VCL for .NET</summary>
<content>    &quot;From a native Delphi application, the whole of .NET is        available via COM interop&quot; excert from article.     What I would like to have and use is the ability to access the whole of Delphi from say a MS excel's VBA IDE window or at least be able to stream a VCL component into a simple userform.-- </content>
</entry>
<entry>
<title>Overview of the VCL for .NET</title>
<author>
<name>Craven Weasel</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33897</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33897</id>
<updated>2003-01-14T05:08:39-08:00</updated>
<published>2003-01-14T05:08:39-08:00</published>
<summary>Overview of the VCL for .NET</summary>
<content>Is there a printer friendly version of this for Europeans?  I think the article deserves a close look1</content>
</entry>
<entry>
<title>re: Overview of the VCL for .NET</title>
<author>
<name>John Kaster</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33892</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33892</id>
<updated>2003-01-13T15:03:26-08:00</updated>
<published>2003-01-13T15:03:26-08:00</published>
<summary>re: Overview of the VCL for .NET</summary>
<content>The VCL for .NET does not support the .NET compact framework.</content>
</entry>
<entry>
<title>Overview of the VCL for .NET</title>
<author>
<name>Eugene Mayevski</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33879</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33879</id>
<updated>2003-01-11T04:56:30-08:00</updated>
<published>2003-01-11T04:56:30-08:00</published>
<summary>Overview of the VCL for .NET</summary>
<content>Hello!Can anybody please explain whether VC.NET supports .NET CF?Sincerely yours,Eugene Mayevski</content>
</entry>
</feed>
