VCL.NET future and support
It seems Borland is committed to extending VCL.NET as their roadmap has
said that is where they expect to have CF design-time support. They
have also said they are taking ECO to VCL.NET.
Many of the third-party components I'm using for several clients support
both VCL and VCL.NET already:
TeeChart - in the latest version just being released
TMS Components Pack Pro
I'd sure like to continue using ReportBuilder rather than having to
switch to RAVE or something else. Does DM still think VCL.NET is only
for trivial applications?
--
Regards,
Paul Breneman
http://www.BrenemanLabs.com/TransPort.htm - TransPort Support
http://www.TurboControl.com/TPSupport.htm - TurboPower support links
said that is where they expect to have CF design-time support. They
have also said they are taking ECO to VCL.NET.
Many of the third-party components I'm using for several clients support
both VCL and VCL.NET already:
TeeChart - in the latest version just being released
TMS Components Pack Pro
I'd sure like to continue using ReportBuilder rather than having to
switch to RAVE or something else. Does DM still think VCL.NET is only
for trivial applications?
--
Regards,
Paul Breneman
http://www.BrenemanLabs.com/TransPort.htm - TransPort Support
http://www.TurboControl.com/TPSupport.htm - TurboPower support links
This discussion has been closed.
Comments
Thanks,
Lars
We are working on a solution that will enable existing ReportBuilder reports
to be leveraged by .NET and VCL.NET applications.
Digital Metaphors is currently working on RB for .NET. The project is being
approached in phases. The first phase will have the ability to preview and
print reports in .NET, while relying on a COM layer to leverage the existing
report engine.
RB .NET <----> Page <--> COM/RB VCL Win32
Later phases will port additional subsystems to pure .NET.
The new development is being done in C#, our intention is to support VS and
Delphi (BDS) .NET environments.
This approach will enable developers to build .NET applications (pure .NET
or VCL.NET) that can preview and print ReportBuilder VCL Win32 reports.
We were excited about VCL.NET when it was announced. We spent over 6 months
porting RB to VCL.NET. The end results were disappointing - poor performance
and poor stability. We shelved the product just prior to completion because
it did not live up to the standards that our customers expect. (Keep in mind
that RB is a development environment and a class library. The RB code base
is large and complex (over 400,000 lines of code). No one was more
disappointed than our team.)
We have not ruled out the possibility of supporting VCL.NET in the future.
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com