Switching to .NET from Borland C++ Builder/Delphi?

  • Thread starter Thread starter Trygve Lorentzen
  • Start date Start date
T

Trygve Lorentzen

Hi,

my company has developed logistics solutions with the Borland developer
product C++ Builder and Delphi. We are considering a switch to .NET with C#.
The following issues are important to us:

* Installer file size (this will be larger since it must include the .NET
framework, right?)
* OS support. Will there be .NET support on Win95/98?
* Drivers and components for the Nexus database engine.
* What is the best way to use some of the existing code in a .NET framework?
COM objects with previously written business logic? Other ways to
incorporate old code?

We were thinking about creating a new solution in .NET and slowly move our
other products to .NET depending on time and demand.

Any other considerations we need to look at? Any experiences with such a
move?

Any help will be GREATLY appreciated!

Cheers,
Trygve
 
* What is the best way to use some of the existing code in a .NET
framework? COM objects with previously written business logic? Other ways
to incorporate old code?
Click to expand...

You might find this link helpful, especially the series of articles
entitled "Head-Spinning". Personally I favour the COM model - a nice
clean separation. I've no idea about the relative performance of the
alternatives.

http://www.codeguru.com/columns/Kate/index.html


Arnold the Aardvark
 
Back
Top