MS的令人难以忍受的更新周期 [英] MS's Excruciating Update Cycles
问题描述
刚刚在VS2005中发现了另一个彻头彻尾的*延迟*错误...这个
时间的方式Application_Startup / w启用应用程序框架
有效（是的） ，这是一个BUG ......它已经在MS社区论坛上提供了医学文件
MSDN ...它涉及在SplashScreen为$ / b时中止Application_Startup $ b set）。
自VS2005发布以来已经差不多5个月了......显然它非常需要a b $ b自发布之日起2.0.1补丁。
这些令人难以忍受的MS补丁周期和MVP辩护者我宁愿等待
来获得经过良好测试补丁"很沮丧。我说要修复BUGS的补丁应该是
很常见。我说，如果一个补丁修补错误的补丁会产生更多的错误，那就是糟糕的DEV而不是缺乏测试。 6个月，8个月，两年
的测试对任何事都没有帮助。 MS必须一起完成他们的行为
。 VS2005虽然整洁而且受到欢迎，但仍然是极其糟糕的（以非常小的方式和令人头疼的方式）。如果期待已久的
" 2.0.1"发布没有提供，我发誓我认为我已经用MS了。
-
-C。 Moya
www.cmoya.com
嗨卡洛斯，
我同意100％与你同意，事实上我遵循频繁的政策错误
修复了我自己的产品（我发布了一个新版本，错误修复了第一天
我所有的MZ-Tools加载项）。我想更大的产品
就像VS 2005需要更多的月份，但我当然也希望更多
频繁的SP（每年至少两次）。
VS 2005的第一个SP计划于2006年第三季度发布：
http://msdn.microsoft.com/vstudio/su...g/default.aspx
对于什么是值得一提的是，它不仅会修复bug，还会引入新的
功能，例如新的Web应用程序项目类型（基于项目，而不是基于文件夹的
，带有我们在VS.NET 2003中的单个输出组件
-
祝你好运，
Carlos J. Quintero
MZ-Tools：Visual Studio的生产力插件
您可以更快地编码，设计和记录：
http://www.mztools.com
&qu OT; CMM" < cm*@nospam.com> escribióenel mensaje
news：eC ************** @ TK2MSFTNGP12.phx.gbl ...刚发现另一个在VS2005中进出*延迟*错误...这个时间的方式Application_Startup / w启用应用程序框架
有效（是的，这是一个BUG ...它已经是doc了在MSDN上的MS社区论坛上......它关注设置SplashScreen时中止Application_Startup。
距离VS2005已经差不多5个月了已经发布......显而易见，它自发布之日起就非常需要一个2.0.1补丁。
这些令人难以忍受的MS补丁周期和MVP辩护者我宁愿等待获得经过良好测试的补丁很沮丧。我说要修复BUGS的补丁应该很频繁。我说，如果一个补丁修补错误的补丁会产生更多的错误，那就是糟糕的DEV而不是缺乏测试。 6个月，8个月，两年的测试对任何事都没有帮助。 MS必须一起完成他们的行为。 VS2005虽然整洁而受欢迎，但仍然极其错误（以非常小而且头脑发热的方式）。如果期待已久的
2.0.1发布没有提供，我发誓我认为我已经用MS了。
-
-C。 Moya
www.cmoya.com
" CMM" < cm*@nospam.com> schrieb：刚刚在VS2005中发现了另一个彻头彻尾的*延迟*错误...这个时间在Application_Startup / w启用应用程序框架的方式
有效（是的，这是一个BUG ......它已经在MSDN上的MS社区论坛中提供了文档...它涉及在设置SplashScreen时中止Application_Startup。
自VS2005发布以来差不多已经过去了5个月......显而易见，它自发布之日起就非常需要2.0.1补丁。
这些令人难以忍受的MS补丁周期和MVP辩护者我宁愿等待
获得经过良好测试的补丁。 abhorent。
我部分同意你的看法。虽然我认为补丁
经过充分测试非常重要，如果它们与安全无关，则应默认发布在
Service Pack中以防止版本丛林，我相信，微软应该在以后的某个时间点发布VS 2005因为软件中已知（可能是未知）的大量错误。我理解微软需要以
的顺序发布他们软件的新版本，以便为他们的员工付钱，但我希望微软
从在发布最终版本之前进行测试和修复bug的时间太短的错误中吸取了教训。
-
MS Herfried K. Wagner
MVP< URL：http：//dotnet.mvps.org/>
VB< URL ：http：//classicvb.org/petition/>
Yikes！由于Q3，因此可能意味着Q3结束或更可能是Q4的开始。
将使VS2005的错误补丁几乎整整一年。 VS2003从来没有
甚至在4年内得到一个单独的...虽然我会冒险说在
恕我直言VS2003比VS2005更加精致....我没有错过MS因为有错误的b $ b。错误是不可避免的。虽然VS2005中的一些错误是他们会错过这个错误吗？头脑风暴，它是一个伟大的产品和
梦幻般的升级。但他们笨拙，过于技术专家（MS需要一个史蒂夫·乔布斯！）和营销驱动的发布周期正在对我的b
尊重和耐心造成影响......我是一名长期的后卫！
-
-C。 Moya
www.cmoya.com
" Carlos J. Quintero [VB MVP]" < CA ***** @ NOSPAMsogecable.com>在消息中写道
新闻：Ox ************** @ tk2msftngp13.phx.gbl ...嗨卡洛斯，
我同意100％与你同意，事实上我遵循频繁的bug政策修复我自己的产品（我发布了一个新的版本，修复了错误的第一天）所有我的MZ-Tools加载项的月份。我认为像VS 2005这样的更大的产品需要更多的月份，但我当然也会更喜欢更频繁的SP（每年至少两次）。
VS的第一个SP 2005年定于2006年第三季度：
http：/ /msdn.microsoft.com/vstudio/su...g/default.aspx
值得一提的是，它不仅会修复错误，还会介绍
新功能，例如我们在VS.NET 2003中使用的新Web应用程序项目类型（基于项目，不是基于文件夹，具有单个输出程序集）
-
致以最诚挚的问候，
Carlos J. Quintero
MZ-Tools：Visual Studio的生产力插件
您可以编码，设计和文档更快：
http://www.mztools.com
CMM < cm*@nospam.com> escribióenel mensaje
新闻：eC ************** @ TK2MSFTNGP12.phx.gbl ...刚发现另一个外出* VS2005中的延迟*错误...这个时间在Application_Startup / w启用应用程序框架的方式中工作（是的，这是一个BUG ......它已经在doc'中了在MSDN上的MS社区论坛......它涉及在设置SplashScreen
时中止Application_Startup。
自VS2005发布以来已经差不多5个月了。 ..显而易见，它自发布之日起就非常需要一个2.0.1补丁。
这些令人难以忍受的MS补丁周期和MVP辩护者我宁愿
等待获得经过良好测试的补丁很沮丧。我说补丁修复BUGS
应该很频繁。我说，如果一个补丁被FIX错误修补了
会产生更多错误，那就是糟糕的DEV而不是缺乏测试。 6个月，8个月，两年的测试不会有任何帮助。 MS必须一起行动。 VS2005虽然整洁而受欢迎，但仍然是极度错误的（以非常小的方式和头脑风暴的方式）。如果期待已久的2.0.1等等。发布没有发布，我发誓我觉得我已经和MS一起了。
-
-C。 Moya
www.cmoya.com
Just discovered yet another out and out *retarded* bug in VS2005... this
time in the way Application_Startup /w the Application Framework enabled
works (yes, it''s a BUG... it''s already doc''d in the MS community forums on
MSDN... it concerns aborting Application_Startup when a SplashScreen is
set).
It''s been almost 5 months since VS2005 has been released... and it was
obvious that it badly needed a 2.0.1 patch since the day it was released.
These excruciating MS patch cycles and the MVP apologists "I''d rather wait
to get a well-tested patch" are abhorent. I say patches to fix BUGS should
be FREQUENT. I say, if a patch that is suppossed to FIX bugs creates MORE
bugs, it is bad DEV and not lack of testing. 6 months, 8 months, two years
of testing isn''t going to help anything. MS has got to get their act
together. VS2005, while neat and welcomed, is nonetheless extrememly
bug-ridden (in really small and head-smacking ways). If the long-awaited
"2.0.1" release doesn''t deliver, I swear I think I''ve had it with MS.
--
-C. Moya
www.cmoya.com
Hi Carlos,
I agree 100% with you, and in fact I follow that policy of frequents bug
fixes for my own products (I release a new build with bug fixes the 1st day
of the month for all my MZ-Tools add-ins). I suppose that bigger products
like VS 2005 require some more months but certainly I would also prefer more
frequent SPs (at least two per year).
The first SP for VS 2005 is scheduled for Q3 2006:
http://msdn.microsoft.com/vstudio/su...g/default.aspx
And for what is worth, it will not only fix bugs but also will introduce new
features, such as a new Web Application project type (project-based, not
folder-based, with a single output assembly) as we had in VS.NET 2003
--
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"CMM" <cm*@nospam.com> escribió en el mensaje
news:eC**************@TK2MSFTNGP12.phx.gbl...Just discovered yet another out and out *retarded* bug in VS2005... this
time in the way Application_Startup /w the Application Framework enabled
works (yes, it''s a BUG... it''s already doc''d in the MS community forums on
MSDN... it concerns aborting Application_Startup when a SplashScreen is
set).
It''s been almost 5 months since VS2005 has been released... and it was
obvious that it badly needed a 2.0.1 patch since the day it was released.
These excruciating MS patch cycles and the MVP apologists "I''d rather wait
to get a well-tested patch" are abhorent. I say patches to fix BUGS should
be FREQUENT. I say, if a patch that is suppossed to FIX bugs creates MORE
bugs, it is bad DEV and not lack of testing. 6 months, 8 months, two years
of testing isn''t going to help anything. MS has got to get their act
together. VS2005, while neat and welcomed, is nonetheless extrememly
bug-ridden (in really small and head-smacking ways). If the long-awaited
"2.0.1" release doesn''t deliver, I swear I think I''ve had it with MS.
--
-C. Moya
www.cmoya.com
"CMM" <cm*@nospam.com> schrieb:Just discovered yet another out and out *retarded* bug in VS2005... this
time in the way Application_Startup /w the Application Framework enabled
works (yes, it''s a BUG... it''s already doc''d in the MS community forums on
MSDN... it concerns aborting Application_Startup when a SplashScreen is
set).
It''s been almost 5 months since VS2005 has been released... and it was
obvious that it badly needed a 2.0.1 patch since the day it was released.
These excruciating MS patch cycles and the MVP apologists "I''d rather wait
to get a well-tested patch" are abhorent.
I partly agree with you. While I believe that it''s important that patches
are well-tested and if they are not security-related should be published in
Service Packs by default to prevent a version jungle, I believe that
Microsoft should have released VS 2005 at a later point of time because of
the huge number of known (and potentially unknown) bugs in the software. I
understand that Microsoft needs to release new versions of their software in
order to get the money to pay for their employees, but I hope that Microsoft
has learned from the mistake of having a too short period of time for
testing and bug fixing prior to releasing the final version.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Yikes! Since "Q3" probably means "End-of-Q3 or more likely Start-of-Q4" that
would make it almost one whole year for a bug patch for VS2005. VS2003 never
even got a single one in 4 years... though I would venture to say that in
IMHO VS2003 was a lot more polished than VS2005.... I don''t fault MS for
having bugs. Bugs are inevitable. Though some of the bugs in VS2005 are "how
they''d miss that?" head-scratchers, it is all-in-all a great product and a
fantastic upgrade. But their lumbering, overly technocratic (MS needs a
Steve Jobs!!!), and marketing driven release cycles are taking a toll on my
respect and patience... and I''m a long-time defender!
--
-C. Moya
www.cmoya.com
"Carlos J. Quintero [VB MVP]" <ca*****@NOSPAMsogecable.com> wrote in message
news:Ox**************@tk2msftngp13.phx.gbl...Hi Carlos,
I agree 100% with you, and in fact I follow that policy of frequents bug
fixes for my own products (I release a new build with bug fixes the 1st
day of the month for all my MZ-Tools add-ins). I suppose that bigger
products like VS 2005 require some more months but certainly I would also
prefer more frequent SPs (at least two per year).
The first SP for VS 2005 is scheduled for Q3 2006:
http://msdn.microsoft.com/vstudio/su...g/default.aspx
And for what is worth, it will not only fix bugs but also will introduce
new features, such as a new Web Application project type (project-based,
not folder-based, with a single output assembly) as we had in VS.NET 2003
--
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"CMM" <cm*@nospam.com> escribió en el mensaje
news:eC**************@TK2MSFTNGP12.phx.gbl...Just discovered yet another out and out *retarded* bug in VS2005... this
time in the way Application_Startup /w the Application Framework enabled
works (yes, it''s a BUG... it''s already doc''d in the MS community forums
on MSDN... it concerns aborting Application_Startup when a SplashScreen
is set).
It''s been almost 5 months since VS2005 has been released... and it was
obvious that it badly needed a 2.0.1 patch since the day it was released.
These excruciating MS patch cycles and the MVP apologists "I''d rather
wait to get a well-tested patch" are abhorent. I say patches to fix BUGS
should be FREQUENT. I say, if a patch that is suppossed to FIX bugs
creates MORE bugs, it is bad DEV and not lack of testing. 6 months, 8
months, two years of testing isn''t going to help anything. MS has got to
get their act together. VS2005, while neat and welcomed, is nonetheless
extrememly bug-ridden (in really small and head-smacking ways). If the
long-awaited "2.0.1" release doesn''t deliver, I swear I think I''ve had it
with MS.
--
-C. Moya
www.cmoya.com
这篇关于MS的令人难以忍受的更新周期的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
