Another thing I should mention is that Delphi handles multi monitors well while Visual Studio doesn't. Every time I minimize Visual Studio, all my windows end up on my primary monitor when I restore it, so I have to move them back to the secondary monitor.
Also, when working remotely and using terminal services, Visual studio windows become undocked, so I need to spend several minutes redocking them and that is very annoying. Overall, Delphi is a much superior product. Sincerely, Brad Gies ------------------------------------- NLM Software Southfield, MI, USA ------------------------------------- > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:delphi-talk- > [EMAIL PROTECTED] On Behalf Of Gies,Brad > Sent: Thursday, July 28, 2005 7:42 AM > To: Delphi-Talk Discussion List > Subject: RE: Delphi compared with Visual Studio and C# > > > I think everything you said is true, and I'd just like to add that > Visual Studio's IDE can be incredibly slow. Overall, I estimate that I > can do about 4 times as much work in Delphi as I can in C#. Some of that > difference can be explained by knowing Delphi much better than C#, but > most of it is due to Delphi just working better. > > > Sincerely, > > Brad Gies > ------------------------------------- > NLM Software > Southfield, MI, USA > ------------------------------------- > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:delphi-talk- > > [EMAIL PROTECTED] On Behalf Of Ford, Allan > > Sent: Wednesday, July 27, 2005 8:45 PM > > To: [email protected] > > Subject: Delphi compared with Visual Studio and C# > > > > > > Some general comments re. Delphi compared with Visual Studio and C# > > ...(These may be useful to someone? Any additional comments welcome > ...) > > > > Delphi has readable operators like "not", "and", "or" rather than ! && > > || ... > > > > Could argue that Pascal leads programmer to better organising their > > code. i.e. Variable declarations are separated from program code. > > Functions and procedures are catalogued upfront. Delphi is much more > > likely to keep self generated code separate from user written code. C# > > can jumble user written items in with designer written items. > > > > Delphi IDE does more for the programmer in terms of component renames > > and automatic code update to match renames. Delphi will remove empty > > procedures that it has created. Visual Studio will leave empty event > > handlers behind .. > > > > It seems..Delphi online Help is more likely to show commonly required > > functionality. It wasn't all that easy finding out how via online help > > how to use C# to open and write to a file when you want to overwrite > the > > file contents if it already exists ... > > > > Delphi has a freeware "delfor" code formatter that can be found on the > > web that does a complete code check and performs indentation for you > > (with preferences settings available). (Visual Studio will do some > > indentation if you remove and re-add the final closing } ) > > Delphi has component help hints built in without requiring a tool-tips > > add-in. > > Delphi application security is not so complicated. i.e. you can run a > > Delphi exe from a network drive. > > Assignment with := and testing with = in pascal compared with = and == > > in C# > > Delphi IDE doesn't have user battling quite so much with properties > form > > wanting to dock everywhere. > > Delphi IDE allows forms to be designed to take up more of the screen, > > guess you can switch to a higher resolution to do similar in Visual > > Studio > > Delphi IDE gives more precise control over windows form control > > position, height, width ... > > Delphi dates are less complicated to work with.. > > Delphi string lists have add("text") (C# programs can be bogged down > > as C# strings are immutable ..i.e. use string builder and append ...) > > Delphi has support for ini files. (you can find C# ini file examples > > via google however.) > > Delphi database result set lets you use > fieldbyname("colname").AsString > > fieldbyname("colname").AsDateTime fieldbyname("colname").AsFloat ... > > which is less verbose in the code than C# calling the Convert class > ... > > > > Delphi has a TMemo component ... C# has textbox with multiline but > then > > you have to use string builder or otherwise strings are handled > > inefficiently and your program response time really bogs down .. > > > > cheers, > > Allan Ford. > > > > > > Santos Ltd A.B.N. 80 007 550 923 > > Disclaimer: The information contained in this email is intended only > for > > the use of the > > person(s) to whom it is addressed and may be confidential or contain > > privileged information. If you are not the intended recipient you are > > hereby > > notified that any perusal, use, distribution, copying or disclosure is > > strictly > > prohibited. If you have received this email in error please > immediately > > advise us by return email and delete the email without making a copy. > > __________________________________________________ > > Delphi-Talk mailing list -> [email protected] > > http://www.elists.org/mailman/listinfo/delphi-talk > __________________________________________________ > Delphi-Talk mailing list -> [email protected] > http://www.elists.org/mailman/listinfo/delphi-talk __________________________________________________ Delphi-Talk mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi-talk
