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# using VS, our intention is to support VS and Delphi .NET environments.
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# using VS, our intention is to support VS and Delphi .NET environments.
Currently we have shelved the .NET solution described below for the time being. It's performance and quality simply did not meet our expectations considering the amount of development that was needed (and support that would be needed in the future).
We would still like to provide a .NET solution for ReportBuilder and look forward to some of the new products and directions CodeGear is exploring, especially Delphi Prism.
A prism version could be interesting, given that dotnet assemblies of various languages can be mixed. That would allow us to develop reports in Prism, but do the bulk of development in c#. Not as nice as pure c#, but nicer than having to screw around with crystal.
A problem is timing. In my view, the window of opportunity for RB is rapidly closing (maybe you have decided it is already closed?). There are other reporting engines, and someone is bound to match RB quality at some point.
Comments
Thanks for your interest in RB for .NET.
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# using VS, our intention is to
support VS and Delphi .NET environments.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
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# using VS, our intention is to
support VS and Delphi .NET environments.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
<<
Nico, I'm sure you can't be precise, but do you have a general time
frame in mind for phase I? 6 mo? 2yrs?
Jeremy
--
Currently we have shelved the .NET solution described below for the time
being. It's performance and quality simply did not meet our expectations
considering the amount of development that was needed (and support that
would be needed in the future).
We would still like to provide a .NET solution for ReportBuilder and look
forward to some of the new products and directions CodeGear is exploring,
especially Delphi Prism.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
http://www.digital-metaphors.com
info@digital-metaphors.com
various languages can be mixed. That would allow us to develop reports
in Prism, but do the bulk of development in c#. Not as nice as pure
c#, but nicer than having to screw around with crystal.
A problem is timing. In my view, the window of opportunity for RB is
rapidly closing (maybe you have decided it is already closed?). There
are other reporting engines, and someone is bound to match RB quality
at some point.
Jeremy