Many years ago, in the middle of 90's, Microsoft has introduced new revolutionary programming technology and named it COM - Component Object Model. Most new OS (Windows) features were implemented using COM. New COM-based programming language was created - Visual Basic. Base Windows language - Visual C++ - has great support for COM. Most programming languages support COM but most of them are not COM-based.
Now new revolutionary technology is proposed by Microsoft - .Net. New OS features are promised to be implemented in .Net, new programming languages are created - C#, VB.Net; Visual C++ can use .Net objects and create new ones. More and more new .Net components become available on the market.
Here is the list of some Win32 applications that host .Net runtime:
- Borland Delphi 8;
- Microsoft Visual Studio;
- C# and VB.Net compilers in .Net framework (csc.exe and vbc.exe), including .Net framework 2 beta;
- Microsoft SQL Server 2005 (Yukon) beta 2 - can host .Net framework to execute stored procedures written in .Net;
- Microsoft Internet information services (IIS) in part that host ASP.Net, including aspnet_isapi.dll;
- Microsoft Internet Explorer 6.0 in part that host .Net controls.
So it is time to support .Net from other Win32 languages such as Delphi.
Managed extensions for VCL -
.Net interop for Delphi Win32
Managed VCL is the best components suite to work with .Net framework from Delphi and C++ Builder - feature named .Net interop. It is designed to provide a way to interact with applications written in anyone of .Net languages - C#, Visual Basic.Net, JScript.Net, Delphi .Net and others.
Managed VCL can:
- Create .Net objects from assemblies not registered for COM, using assembly name or location, and loading .Net assemblies from streams;
- Create and use .Net objects that are not COM visible;
- Create .Net objects using parametrized constructors;
- Call properties/methods/fields of .Net object including static properties/methods/fields;
- Handle .Net exceptions and get all .Net exception properties including exception type name, StackTrace etc.;
- Get information about loaded instance of .Net framework such as memory usage and size of heap by generation;
- Load needed .Net runtime and even select which version of runtime to use on startup;
- Place .Net controls on VCL Win32 form;
- Use ADO.Net datasources as TDataSet descendants in Win32 applications. ADO.Net will be native and most supported API for SQL Server 2005 (Yukon);
- Host ASP.Net pages and services;
- Embed .Net assemblies into Win32 application as resources.
Managed VCL can not:
- Query .Net interface if it is not COM visible.
- Work with .Net events.
- Managed VCL will not turn your Delphi or C++ Builder into .Net language and it some other features may not be available.
Managed VCL includes special components for:
- ADO.Net - supports almost all ADO.Net features. Components to work with all standard .Net providers (those that are available in .Net framework) are included. ADO.Net will be most supported interface for MS SQL Server 2005 (Yukon).
- JScript.Net - lets you execute JScript.Net scripts from Delphi/C++ Builder application.
- ASP.Net - process ASP.Net pages and services from Win32 applications.
Managed VCL is available for Delphi 5, 6 Delphi 7, 2005, 2006, 2009, 2010, XE, XE2, XE3, C++ Builder 5, 6, 2009, 2010, XE, XE2.
Trial version will work 30 days.
- $125 without source code
- $250 with source code
- Discounts for bulk purchases.
Forums are available on http://www.managed-vcl.com/phpBB3_2.
If you have questions about Managed VCL or want to send bug-report, please write email@example.com