Cross Ref > Tool Basics
By Mike Prestwood
ASP Classic versus Delphi Prism: A side by side comparison between ASP Classic and Delphi Prism.
Developer environment basics such as common file extensions, common keyboard shortcuts, etc.
ASP Classic:
With ASP Classic, you simply copy your files to a web server that is capable of running ASP pages. This includes your .ASP pages along with supporting files such as images, include files, and database files.
Optionally, you can also deploy a global.asa file which is used to code certain events like application start, application end, session start, and session end.
More Info / Comment
Delphi Prism:
Prism projects require the .Net framework and any additional dependencies you've added such as Crystal Reports.
In Visual Studio.Net, you can create a Setup and Deployment project by using any of the templates available on the New Project dialog (Other Project Types).
Prism doesn't directly support ClickOnce . At least not yet. In other words, there isn't a Security tab on the solution properties dialog. To create a ClickOnce deploy package, search the internet for mage.exe and mageui.exe .
In addition, you can use any of the many free and commercially available installation packages.
Languages Focus Primary development tool(s) used to develop and debug code.
ASP Classic:
Microsoft Visual Interdev was popular for several years but isn't used as much any more. Any good editor such as Microsoft Expression Web, etc. will work but debugging is left up to interactive skills.
More Info / Comment
Delphi Prism:
Delphi.Net first shipped as a compiler only with Delphi 7. Delphi 8 is a .Net dedicated solution (no Win32) but was not clearly better than VS.Net so more developers moved to VS.Net and bypassed Delphi 8. Delphi for .Net shipped with Delphi 2005, 2006, and 2007 but languished because of a lack of development and VS.Net clearly implemented more .Net CLS features than Delphi for .Net. Delphi Prism (Oxygene) strives to keep pace and in some cases out pace C# and VB.Net using the Object Pascal language.
More Info / Comment
Languages Focus Common or primary file extensions used (not a complete list, just the basics).
ASP Classic:
.ASP
.asp is the default extension for Active Server Pages (ASP) although some developers will change the default extension in an effort to add an additional security level. Although there is no clear standard for include files, using .INC is common but you must make sure that .INC files are not executed nor displayed.
More Info / Comment
Delphi Prism:
Delphi Prism common source code file extensions include:
.SLN - Solution File. Contains solution specific information such as links to the projects within this solution.
.Oxygene - Project File. Contains project specific information but this is not the Delphi-like project file Delphi developers are used to. This is the VS.Net project file.
Program.pas - This is the Delphi-like .dpr project-equivalent file and contains the Main method which is the entry point for the executable. All .NET projects except for DLLs needs one.
.pas - Delphi Prism source file (same extension as Delphi for Win32).
.Designer.pas - Prism form file (a text resource file).
More Info / Comment
ASP Classic:
Language Overview: Class-based language. Although you can create classes, ASP is not fully OOP. It is a traditional language with a few OOP extensions. You code in a traditional approach using functions, procedures, and global data, and you can make use of simple classes to help organize your reusable code.
Target Platforms: ASP Classic is most suitable for creating websites targeting any browser (IIS Web Server with ASP Classic installed or equivalent).
More Info / Comment
Delphi Prism:
Language Overview: Prism is a type safe language and a fully OOP language (no global functions or variables except for a very special __Global class). You code using a fully OOP approach (everything is in a class) but you have the additional benefit of a hybrid language using a special __Global class. Prism targets the .Net CLR and Mono. Based on Borland's original work with Delphi.Net and then continued by RemObjects as Oxygene, and now co-developed by CodeGear and RemObjects.
Target Platforms: Delphi Prism is most suitable for creating .Net Framework applications. This includes desktop business application using WinForms and websites using WebForms.
More Info / Comment
Languages Focus Built-In: Some development tools have a reporting tool built-in and some do not. For example, typically desktop databases such as Paradox and Access have a built-in reporting tool and typically that reporting tool is used with nearly every application built with it. A built-in reporting tool makes development of reports across many clients and applications consistent and therefore easy.
Add-On: Development tools that do not have a built-in reporting tool need to use either a currently bundled report writer, or one of the popular reporting tools that integrates well with the development tool. For example, popular reporting tools include Crystal Reports, ReportBuilder, and MS SQL Reporting Services (tied to MS SQL).
ASP Classic:
No built-in report writer but because ASP Classic targets a client browser (a document interfaced GUI), a common solution is to simply output an HTML formatted page with black text and a white background (not much control but it does work for some situations).
More Info / Comment
Delphi Prism:
For WebForm applications the client target is the browser (a document interfaced GUI), a common solution is to simply output an HTML formatted page with black text and a white background (not much control but it does work for some situations).
For WinForm applications Rave Reports and Crystal Reports are very popular with Delphi Prism and Delphi for .Net developers.
More Info / Comment