Borland rises to .net challenge with new development suite


Borland rises to .net challenge with new development suite

Borland is rising to Microsoft's Visual Studio .net challenge with a new software development suite based on Delphi, writes Eric Doyle.

For many years, Microsoft has been in a head-to-head battle with Borland to win over the development community to its tool set, with no outright winner. The functionality concentrated in Visual Studio has been a challenge for Borland but its highly praised Delphi software has helped to maintain its prominence. Now the company is fighting back with Enterprise Studio for Windows.

To produce the suite, Borland has been working with partners such as Rational and Boldsoft to integrate their individual packages into a single development environment. Borland claims this gives wider scope than Microsoft's .net focus to provide additional support for platforms such as Sun One. Enterprise Studio can also be supplied with Macromedia's Dreamweaver Ultradev4 for Web site development.

The suite features Borland's Delphi 6, a rapid application development tool that can be used for developing Web services using the XML, Soap, XSL (Extensible Stylesheet Language) and WSDL (Web Services Description Language) standards.

It also includes Rational Rose Professional Data Modeller Edition, which provides a co-operative development environment to Unified Modelling Language standards, for software development teams; the Rational Unified Process collection of guidelines, templates and examples to enhance team productivity; and the Bold for Delphi business object framework.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

This was first published in January 2002


COMMENTS powered by Disqus  //  Commenting policy