Re: Visual Studio Sucks

Three thoughts come to mind as I read this?

VI sucked 10 years ago when it was new. Why in the world would you still be
using this non-supported product today?

It sounds to me like you are just extremely used to the way VI works (using
that term loosly) and just perhaps if you acknowledged that this is the
basis for most of your gripes, you could embrace what VS does infinately
better than VI.

You are comparing apples and watermelons. These two products aid in the
development of applications that run on entirely different platforms.

-Scott


"Bookham Measures" <bookham_measures@xxxxxxxxxxxxxxx> wrote in message
news:14FABEAB-2068-46D9-A5D5-3D444D738B49@xxxxxxxxxxxxxxxx
Hello

I have recently moved from Visual Interdev 6 to Visual Studio 2005. What
a complete load of garbage the Query Builder IDE is. Why have they made a
wholly useful environment tool into a clumsy, awkward and less intuitive
beast?

Perhaps you guys could help me understand the following:

1) Why when I choose "Stop Outlining" in a Stored Procedure text window,
from the context menu, does it do nothing?

2) Why were the keyboard shortcuts/access keys removed from the context
menu in the same stored procedure design window? (e.g. in VI 6 I could
bring up a new query builder via the keyboard by doing Shift F10 and then
I. Now I have to use the mouse.

3) Why does the query builder IDE not dock into the main workspace? Why
did they make it a modal dialog?

4) When working with SQL Server - why the heck did they remove the columns
Identity and Default value from the query builder/table designer IDE?
This is my biggest gripe to be honest. Having to locate these fields in
the revolting properties pane is a nightmare, and of course, requires
mouse action in place of key strokes.

Everyone I have spoken to thus far says that the new environments are far
more awkward to use and things take more time to perform.

I have found this to be true of SQL Server Management Studio also, a huge
backwards step in terms of usability for anyone who uses the product on a
daily basis. There was nothing wrong with the way things worked in SQL
2000 Enterprise Manager coupled with Query Analyser.

Has anyone managed to get VI6 to function properly with SQL 2005, in terms
of designing and saving stuff? I am contemplating downgrading our
development environment back to SQL 2000.

Thanks

David


.

Relevant Pages

  • Re: Visual Studio Sucks
    ... In order to use outlining, you have to select the entire block you want ... a complete load of garbage the Query Builder IDE is. ... When working with SQL Server - why the heck did they remove the columns ... I have found this to be true of SQL Server Management Studio also, ...
    (microsoft.public.vsnet.ide)
  • Query builder enclosing fieldnames in quotes
    ... I'm trying to use the Trim function in the Query builder, ... with one SQL statement: ... I then went into Design view, and added all my other fields and tried to ... When I go into the Update To part to delete the quotes, ...
    (microsoft.public.access.queries)
  • Req: SQL Developer / DBA
    ... SQL Server Developer & DB Administrator ... The person will provide database expertise in SQL development, ... databases, design and implementation. ... version control, object management, standards, code & design review, ...
    (microsoft.public.sqlserver.dts)
  • Req: SQL Developer / DBA
    ... SQL Server Developer & DB Administrator ... The person will provide database expertise in SQL development, ... databases, design and implementation. ... version control, object management, standards, code & design review, ...
    (comp.unix.shell)
  • Req: SQL Developer / DBA
    ... SQL Server Developer & DB Administrator ... The person will provide database expertise in SQL development, ... databases, design and implementation. ... version control, object management, standards, code & design review, ...
    (comp.databases.ms-sqlserver)