受VS2005影响不足 [英] Underwhelm by VS2005
问题描述
让我先说我喜欢VS2005。它改进了很多东西
缺乏VS 2003并且几乎没有任何东西。话虽如此，我觉得它有点不知所措。
尽管有一些新的控件，仍然缺乏质量
控制甚至建立一个基本的Windows应用程序。例如，MDI是一种
技术，被微软自己认为是1995年（11年之前的b $ b！）...但是我们必须建造大量的代码或求助于第三方
解决方案，以获得某种体面的标签SDI / MDI窗口管理（其中
MDI子项显示为选项卡）解决方案就像在Visual Studio
IDE本身或FrontPage，FireFox等应用程序。为什么会这样？为了天堂的缘故，这不是关于
的时间吗？
虽然数据集现在包含*一些*整洁的改进，但我不能揣摩
微软花费时间的一些原因。关于数据集的全部好处是，它们与
数据库完全分离。并且只使用离散（和可选）
DataAdapter（以及它非常有用的TableMappings功能）捆绑在一起。
我们应该在VS 2005中获得的是一个更好的更漂亮的wysiwig（拖动
和drop）编辑器，用于将db列映射到Dataset元素。相反，我们得到了一个相当无用的TableAdapter功能，它吹出了很多物理上的想法，从水中分离层数（在远程物理上是n层的
$ b）至少$ b分布式应用程序）。我的意思是，它甚至不支持
交易（没有kludging）。随着时间的推移，我认为这是新的。功能将
证明与CommandBuilder一样无用。
为什么不能从网络共享安装和运行MSDN？ （它甚至不能从光盘上运行）这对我来说似乎很荒谬。此外，在线指的是在线。 MSDN
集成是gee-whiz整洁...但有点无用，因为它缺少索引
和可浏览的内容。
为了改变，很多其他的东西似乎都是变化......对于
实例：
为什么要移动查看代码/"查看设计师解决方案中的按钮
资源管理器？...并且无法将其移回原来的位置！这个
按钮已经在过去10年以上的确切位置（在旧VB中最少
）...现在移动它的重点是什么？每当我（反思地）
点击它曾经的位置时，我会得到属性。窗口。为什么？！！！！事实上，
" Properties"经过多年的经验，与右键单击上下文菜单相关联的
是一种东西。栏上的那个按钮
的整个想法是可疑的，更不用说它是吧台上的第一个按钮。
< blockquote> CMM，
当我开始阅读您的消息时，我明白了，CMM将以
的价格与Visual Studio达成一致。
但请注意，不能保证现在的行为将保持不变，罗马不会在一天内建成。
除了最后一个，我想CMM是如何为用户推出新的
的东西，即使按钮位置的最轻微变化也是如此
他/她很难接受。
只是我的想法，
Cor
" Cor Ligthert [MVP]" <无************ @ planet.nl> schrieb：但请注意，不能保证现在的行为会保持不变，罗马不会在一天内建成。
好吧，如果行为经常变化，就像在沙滩上建房子一样。找到一个更稳定的房子建造基地会更好。
-
MS Herfried K 。瓦格纳
MVP< URL：http：//dotnet.mvps.org/>
VB< URL：http：//classicvb.org/petition/ >
我真的不想要按钮的位置。我一直在使用什么
似乎是过去10年来改变而没有至少具备将其恢复原状的能力
。这就像把大堂的按钮
一直放在我的电梯里一样。
这看起来像是一个小问题..但是，实际上它只是表明
下坡。申请减少。虽然VS 2002和2003似乎已经开发出了对IDE过去几年的崇敬（以及对它们的改进了b / b
），但是它们仍然存在VS 2005似乎已经完成了使用众多可怕的Java IDE作为模板完成了
（完整的非
标准和丑陋的工具箱标签似乎有由初级
程序员而不是GUI图形专家开发。
" Cor Ligthert [MVP]" <无************ @ planet.nl>在消息中写道
news：％2 **************** @ TK2MSFTNGP14.phx.gbl ...CMM，
当我开始阅读你的消息时，我明白了，CMM将会与他作为Visual Studio的附加内容达成一致。
然而要注意我们无法保证现在的行为会保持不变，罗马不会在一天内建成。
除了最后一个，我还想到了CMM想要怎么做为用户介绍新的东西，即使按钮的最轻微变化也是为了让他/她难以接受。
只是我的想法，
Cor
Let me preface by saying that I like VS2005. It improves on many things
lacking in VS 2003 and takes pretty much nothing away. Having said that, I
am a little underwhelmed by it.
Despite a couple of some new controls, there is still a dearth of quality
controls to build even a rudimentary "Windows" app. For instance, MDI is a
technology that was deemed passe in 1995 by Microsoft itself (11 years
ago!!!)... yet we have to build tons of code or resort to a third party
solution to get some sort of decent tabbed SDI/MDI Window management (where
MDI Children appear as tabs) solution like that found in the Visual Studio
IDE itself or apps like FrontPage, FireFox, etc. Why is this? Isn''t it about
time for heaven''s sake?
Although the Dataset now contains *some* neat improvements, I can''t fathom
the rationale for some of the stuff Microsoft spent time on. The whole great
thing about Datasets is that they were completely decoupled from a
"database" and only tied together using a discrete (and optional)
DataAdapter (together with it''s extremely useful TableMappings feature).
What we should have gotten in VS 2005 was a better more pretty wysiwig (drag
and drop) editor for mapping db columns to Dataset elements. Instead we get
the rather useless TableAdapter feature that blows many ideas of physical
separation of layers out of the water (in remoted physically n-tiered
distributed apps at least). I mean, it doesn''t even really support
transactions (without kludging). In time, I think this "new" feature will
prove as useless as the CommandBuilder.
Why can''t MSDN be installed and run from a network share? (It can''t even be
run from the disc) That seems ridiculous to me. Also, the "Online" MSDN
integration is gee-whiz neat... but kinda useless because it lacks an Index
and browsable Contents.
Lots of other things just seem like change for the sake of change... for
instance:
Why move the "View Code"/"View Designer" buttons in the Solution
Explorer?... and with no option to move it back to where it used to be! This
button had been in that exact location for the last 10+ years (in old VB at
least)... what was the point of moving it now? Every time I (reflexively)
click where it used to be, I get the "Properties" window. Why?!!!! In fact,
"Properties" is something that after years of experience is intiuitevly
associated with the right-click context menu. The whole idea of that button
being on the bar is dubious let alone it being the FIRST button on the bar.
CMM,
When I started to read your message I got the idea, CMM will be reach with
what he can make as additions to Visual Studio.
However be aware that there is no guarantee that the behaviour as it is now
will stay the same, Rome was not build in one day.
In addition to the last, I thought how does CMM want to introduce new
things for users, even the slightest change in th place of a button is for
him/her difficult to accept.
Just my thought,
Cor
"Cor Ligthert [MVP]" <no************@planet.nl> schrieb:However be aware that there is no guarantee that the behaviour as it is
now will stay the same, Rome was not build in one day.
Well, if behavior changes too often it''s like building houses on sand. It''s
better to look for a more stable base for building the house.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
I don''t really want the "place of a button" that I have been using for what
seems like the last 10 years to change without at least having the ability
to put it back to where it was. It''s like putting the button for the Lobby
in my elevator all the way at the top.
It might seem like a minor issue... but, really it''s just an indication of a
"downhill" decline of an application. While VS 2002 and 2003 seem to have
been developed with a reverence for the IDE''s of years past (and an
improvement on them), the loock and feel of VS 2005 seems to have been done
using the multitude of horrible Java IDE''s as a template (complete with non
standard and ugly toolbox tabs that seem to have been developed by a junior
programmer instead of a GUI graphics expert).
"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...CMM,
When I started to read your message I got the idea, CMM will be reach with
what he can make as additions to Visual Studio.
However be aware that there is no guarantee that the behaviour as it is
now will stay the same, Rome was not build in one day.
In addition to the last, I thought how does CMM want to introduce new
things for users, even the slightest change in th place of a button is for
him/her difficult to accept.
Just my thought,
Cor
这篇关于受VS2005影响不足的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
