Re: Give me reasons not to use Delphi

From: Harry Van Tassell (hairy_at_nada.com)
Date: 01/05/04 

Date: Mon, 5 Jan 2004 08:00:09 -0500

David Clegg wrote:
> Bruce McGee wrote:
>
>> Has anyone here run into serious problems with any version of Visual
>> Studio?
>
> I've only been using VS.NET 2003 for approx 3 weeks, but so far I am
> not very impressed with its stability (or performance for that
> matter). It seems to freeze at the drop of a hat, but the most
> frustrating part is that when it does, you cannot kill the process.
> And AFAIK, there's no SP for it. Anyone know where I can download the
> MS QC client so I can enter a request for a SP and muster votes for
> it? ;-)

Well Sir, may I kindly suggest that you place your hat on the floor while
programming in VS.NET.<g>

I'll certainly agree that I wish it was a bit faster but stability hasn't
been a problem for me since the beta-1 days. Much of that went away with
beta-2 in June, 2001 which proved to be quite usable. I haven't been at all
plagued with the stability problems you report. On occasion I've had the
IDE throw a critical error and when it does the error dialog presents a
button to press to file an e-mail bug report to Microsoft The beta versions
even had a similar bug report button on the IDE toolbar - a practice that
Borland should emulate.

Now I have had instances of hang-ups when debugging but these have been
because my application contained some dumb coding mistake I made and I've
been able to kill the debug process from the Win2K task manager. Recently I
did have some IDE stability problems but that was while beta testing a new
IDE add-in and it went away when I uninstalled the add-in.

If want to report a compiler generated bug to Microsoft then you can
lookup "bug reporting" in the VS help file where you will find the procedure
listed below for making an e-mail bug report to Microsoft. I like this a lot
better than the QC Client concept - why nor make it as simple as possible
with automation for the collection of pertinent info so that the bug report
is more meaningful and easier to analyze.

--Hairy <dedicated to fair and balanced FUD busting>

------
/bugreport (Report a Problem)See Also
C# Compiler Options/bugreport:file
where:
file
The name of the file that you want to contain your bug report.
Remarks
The /bugreport option will cause the following information to be placed in
file:
A copy of all source code files in the compilation.
A listing of the compiler options used in the compilation.
Version information about your compiler, runtime, and operating system.
Referenced assemblies and modules (saved as hexadecimal digits), except
assemblies that ship with the .NET Framework SDK.
Compiler output, if any.
A description of the problem, which you will be prompted for.
A description of how you think the problem should be fixed, which you will
be prompted for.
Because a copy of all source code files will be placed in file, you may want
to reproduce the (suspected) code defect in the shortest possible program.
To set this compiler option in the Visual Studio development environment
This compiler option is unavailable in Visual Studio.
To set this compiler option programmatically
This compiler option cannot be changed programmatically.
Example
Compile t2.cs and put all bug reporting information in the file problem.txt:
csc /bugreport:problem.txt t2.cs 

----