 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / IDE / December 2004Why does MS play these FIX games???
One of *MANY* 'available' fixes for VS (and related): http://support.microsoft.com/default.aspx?scid=kb;en-us;822759 But, you have to play the "contact Microsoft Product Support Services to obtain the fix" game -- *WHY*??? What is the malfunction over in Redmond that disallows posting these fixes in a readily-obtainable location, or _better_yet_, how about _service_packs_ for VS? Every hotfix is then included into a service pack. Service pack goes through much more rigorous regression testing than individual hotfix. Therefore it is safe to recommend everyone to install SP. However, you should only install hotfix if you do experience the problem. There is certain probability that hotfix may break something else since it did not go though full test pass that VS QA performs for betas, product releases and service packs. Full test pass takes a lot of time and resources and cannot be performed for every small fix. Thanks Mikhail Arkhipov (Microsoft) -- This post is provided 'AS IS' with no warranties and confers no On 12/15/04 9:51, in article 41C079A7.C2455409@classicade.com, "Bret Pehrson" <bret@classicade.com> wrote: > One of *MANY* 'available' fixes for VS (and related): > [quoted text clipped - 8 lines] > readily-obtainable location, or _better_yet_, how about _service_packs_ for > VS? Please, when we could expect the SP for vs.net 2003 ? Thank you, Tomas Hejny > Every hotfix is then included into a service pack. Service pack goes through > much more rigorous regression testing than individual hotfix. Therefore it [quoted text clipped - 25 lines] > > readily-obtainable location, or _better_yet_, how about _service_packs_ for > > VS? > Every hotfix is then included into a service pack. Service pack goes through > much more rigorous regression testing than individual hotfix. Therefore it [quoted text clipped - 8 lines] > > Mikhail Arkhipov (Microsoft) ??? You guys _aren't_ doing service packs! Last one that I'm aware of was for VC 6, and we are 2 betas past that. That is part of my original issue, ramp up whatever you need internally and get the SPs out there! > -- This post is provided 'AS IS' with no warranties and confers no > [quoted text clipped - 13 lines] > > readily-obtainable location, or _better_yet_, how about _service_packs_ for > > VS? both versions of visual studio .net have had service packs released for them... http://www.microsoft.com/downloads/details.aspx?FamilyID=A8F5654F-088E-40B2-BBDB -A83353618B38&displaylang=en >> Every hotfix is then included into a service pack. Service pack goes through >> much more rigorous regression testing than individual hotfix. Therefore it [quoted text clipped - 34 lines] >> > readily-obtainable location, or _better_yet_, how about _service_packs_ for >> > VS? > both versions of visual studio .net have had service packs released > for them... > > http://www.microsoft.com/downloads/details.aspx?FamilyID=A8F5654F-088E-40B2-BBDB -A83353618B38&displaylang=en They didn't. What you refer to as Visual Studio service packs are actually .NET framework service packs. Those two are not the same. VS.NET 2003 Service Pack is long overdue IMHO.  SignatureSergey M http://www.usysware.com/dpack/ >> both versions of visual studio .net have had service packs released >> for them... [quoted text clipped - 4 lines] >actually .NET framework service packs. Those two are not the same. >VS.NET 2003 Service Pack is long overdue IMHO. ok, granted that the service packs had mostly framework updates, i believe they also fixed some vs problems. i base this on the resolution section of the bug being reported in this thread: "A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix." > "A supported fix is now available from Microsoft, but it is only > intended to correct the problem that is described in this article. [quoted text clipped - 3 lines] > you wait for the next .NET Framework service pack that contains this > fix." Which is what the OP was complaining about. The hoops you have to go through to get any VS.NET fixes (note that .NET framework is *NOT* VS.NET). It's high time for both VS.NET and VS.NET 2K3 to get SP1 to deal with the bug fixes. I had a major one in the original VS.NET, and was told a 2K3 upgrade was the only fix. Luckily, it was during the $35 upgrade period, and I wanted the better ISO compliance of 2K3 anyways. But they still need to support their customers better. > It's high time for both VS.NET and VS.NET 2K3 to get SP1 to deal with > the bug fixes. I had a major one in the original VS.NET, and was told a > 2K3 upgrade was the only fix. Luckily, it was during the $35 upgrade It was the same here, but we couldn't even get the $35 upgrade (in Hungary). We are still waiting for the first VS.NET2002 service pack.. Happy new year, Microsoft. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.