Re: Visual Studio Sucks



"Bookham Measures" <bookham_measures@xxxxxxxxxxxxxxx> wrote in message
news:7512C4AB-DC8F-4B2E-A2D3-4308E6EB494F@xxxxxxxxxxxxxxxx
Scott

You emphasize that this was 10 years ago and that is my entire point! 10
years ago it was simple to work with databases, tables and stored
procedures in Visual Interdev, (regardless of what programming language
you were using).

I think if you investigate VS more, you'll find it extremely easy to do
everything you used to do and more.


Now, this task is harder.

Perhaps I am over familiar with VI,

This is my point. You've been using VI for so long, of course you are
experienced and proficient with it and, of course, using anything else will
not be as productive for you until you are as proficient with it as you are
VI. I happen to find working in Notepad still a very proficient way of
working on certain applications, but I recognize that this is not the
general view and the reasons I like it for certain things are not shared by
the mainstream.

but requiring a user to use the mouse to do things that could previously
be performed by the keyboard seems totally backward in my view. It is the
"Data Environment" I am referring to.

You are entitled to your opinion, of course, but I think if you ask most
people, they'll say that using the mouse instead of laborious typing is
easier.



"Scott M." <smar@xxxxxxxxxxxxx> wrote in message
news:#0j68#$PIHA.5184@xxxxxxxxxxxxxxxxxxxxxxx
I'd accept that as a generality. You can't compare WinForms and WebForms
designers at all since they really have no commonalities between them
other than they both serve to help build UI's, but UI's of completely
different types. We'll see if WPF and XAML can help resolve this issue.

You also can't compare VI and VS since they were/are designed to build
completely different types of web applications. Not, to mention that VI
was buggy and difficult to work with on its best day and that day was 10
years ago.



"CMoya" <moy@xxxxxxxxxx> wrote in message
news:2ABC832F-DE0C-43C7-A893-E2221F4E5924@xxxxxxxxxxxxxxxx
I'm not saying that you're wrong (VS.NET does many many things right),
but I understand the OP's gripes. Sometimes it behooves us to remember
some of the things that were done RIGHT in the past, to understand how
to improve them today. This is especially true in VS.NET's "Webforms"
designers... which lag incredibly compared to their Winforms
counterparts.

"Scott M." <smar@xxxxxxxxxxxxx> wrote in message
news:eUJCvsrPIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
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
    ... This is especially true in VS.NET's "Webforms" designers... ... What a complete load of garbage the Query Builder IDE is. ... Why when I choose "Stop Outlining" in a Stored Procedure text window, from the context menu, does it do nothing? ... 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
    ... 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
    ... You can't compare WinForms and WebForms ... This is especially true in VS.NET's "Webforms" designers... ... What a complete load of garbage the Query Builder IDE is. ... When working with SQL Server - why the heck did they remove the ...
    (microsoft.public.vsnet.ide)
  • RE: Charging customers on security
    ... The key issue would seem to be what the expected environment of a piece ... malicious attacks and to have designers whose ability to ... Subject: Charging customers on security ... I think your idea of layered security will work quite well. ...
    (SecProg)
  • 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)