Visual Studio Sucks

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
    ... a complete load of garbage the Query Builder IDE is. ... menu in the same stored procedure design window? ... 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)
  • Re: Visual Studio Sucks
    ... This is especially true in VS.NET's "Webforms" designers... ... It sounds to me like you are just extremely used to the way VI works 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. ... What a complete load of garbage the Query Builder IDE is. ... 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. ...
    (microsoft.public.vsnet.ide)
  • 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)
  • ORACLE CLIENT USERS BEWARE: Bug in Query Builder breaks SQL
    ... it will work fine using the conversion wizard, but if you try to view the SQL ... go to generate the command objects with the dreaded "Syntax Error: ... large projects that use Oracle table joins. ... When trying to use the Query Builder with Oracle, ...
    (microsoft.public.vsnet.general)
  • Re: Visual Studio Sucks
    ... "Data Environment" I am referring to. ... designers at all since they really have no commonalities between them ... I could bring up a new query builder via the keyboard by doing Shift ... When working with SQL Server - why the heck did they remove the ...
    (microsoft.public.vsnet.ide)