C
Cor Ligthert [MVP]
However, I think that it's better to have only few versions of a certain
Cor
Exact
Cor
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
C
CMM
Look, we can all point out what's great about VS2005. We're all using it,
right? And we can all point out nice-to-haves wishes that aren't "bugs."
Fact of the matter is that there indeed many bugs in this "1.0" release.
Waiting a year to see them patched is insane.
right? And we can all point out nice-to-haves wishes that aren't "bugs."
Fact of the matter is that there indeed many bugs in this "1.0" release.
Waiting a year to see them patched is insane.
C
CMM
However, I think that it's better to have only few versions of a certain
Why??? Please qualify your statement.
I mean, isn't modern componentized development practices suppossed to
alleviate this "classic notion." This may have been true in the days of
pre-MSI, monolithic applications, and DLL hell. But, not today.
In fact I would argue that you're 100% wrong... because *smaller* updates
encourage everyone to be using the "same" version. As a user, I'm more open
to installing small updates that I can easily rollback were something to go
wrong. However, the big bad Service Packs scare me as it does most IT
Managers.
Why??? Please qualify your statement.
I mean, isn't modern componentized development practices suppossed to
alleviate this "classic notion." This may have been true in the days of
pre-MSI, monolithic applications, and DLL hell. But, not today.
In fact I would argue that you're 100% wrong... because *smaller* updates
encourage everyone to be using the "same" version. As a user, I'm more open
to installing small updates that I can easily rollback were something to go
wrong. However, the big bad Service Packs scare me as it does most IT
Managers.
C
Carlos J. Quintero [VB MVP]
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/support/servicing/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
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/support/servicing/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