Visual Basic perf fixes to issues with large VS2005 solutions / projects

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

Colin Blair — Tue, 25 Jul 2006 21:11:00 GMT

Why do we have to call support to get hotfixes for Visual Studio? Why can't we just download them? If you really want to track them, make us login first if you have to. Calling support is a huge pain.

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

cmayo — Thu, 27 Jul 2006 23:44:38 GMT

Thanks for your comment. I’m the Program Manager responsible for the performance of Visual Basic 2005 and my team created this QFE.

I understand that having to call support to get a QFE is inconvenient relative to a public download. We create QFEs in order to quickly address issues that customers are experiencing in production that we did not see in testing. While QFEs are tested rigorously, they are not tested to the same level of scrutiny that we tested Visual Studio 2005 before release. Because of this, we ask that you call support to get the fix so we can track the fix over time. This fix will be publicly available in SP1, due to be released later this year.

Thanks,
Chris Mayo
Visual Basic Performance Program Manager

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

Eric — Thu, 03 Aug 2006 20:43:27 GMT

Chris,

Can you be more specific about the timeframe? I take it that the September release date is no longer accurate.

This QFE rule may be convenient for you, but it wastes alot of our time. I
have always found it absurd that any schmuck can download a beta OS from Microsoft, but developers must jump through hoops to get a simple fix.

Traditionally, QFE's were meant to target specific problems and were generally very narrowly defined, and tended to address issues that only applied to a very small group of users. For example:

"Visual Studio .NET 2003 Stops Responding During the Solution Build Process if You Have Compuware DriverStudio Installed"

I can see how that might not have come up in testing. I cannot see how the broad situations described in 917452 and 920805 didn't. They are environmental issues that indicate that 2005 was not ready for prime time when it was released. They represent the pain that those of who use this sloth on a daily basis experience.

Furthermore, since so many of these QFE go back to msenv.dll, your're not installing 1 hotfix, but every fix that contained that same assembly dependency that has already been released. Resharper 2.0 REQUIRES and installs one of these msenv.dll hotfixes. Kinda violates the QFE definition, doesn't it?

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

cmayo — Tue, 15 Aug 2006 22:57:40 GMT

Thanks for the feedback, Eric.

I agree that getting a hotfix should be much easier than it is today. We're working on making getting a hotfix roughly as quick and easy as a downloading a beta product, per your suggestion. I'll post our plans on the VB Blog (http://blogs.msdn.com/vbteam/default.aspx) and this thread as they become more firm.

I did call support yesterday to get the fix myself, and it did take about 15 minutes. While this is not as quick as a web download, we've made every effort to make it quick and painless.

Let me know if you get a different experience when you call support.

Thanks,
Chris Mayo
Visual Basic Performance Program Manager

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

Earl Wynne — Sat, 09 Sep 2006 16:36:33 GMT

I really hope that the sp1 has a LOT more than what the hotfix does. I currently have a very large application and I spend most of my time waiting for the IDE. If only I would have known I would have stayed with the 2003 version and just made due.

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

Amit Vij — Mon, 18 Sep 2006 23:00:40 GMT

I also agree that calling to get a hotfix is a big pain. I discovered on a Friday evening that you have to call, and it seems the hotfix hotline isn't even available 24-7. They are actually closed on the weekends... I had to wait till Monday to get a link to download the hotfix and the special hotline operator did nothing extra than the regular MS contact reps other than email a link. I think this is a very poor system.

The hotfix dwindle my compiling time from 5mins to 2mins. If this was the same project in VS 2003, it would take under 30 seconds.

The Hardware of ASP.NET Programming

Stephen Wright — Thu, 21 Sep 2006 19:55:54 GMT

Greetings to all! After working with ASP and then ASP.NET, and now with version 2.0, I&#39;ve programmed

Temp Post for Review: Optimizing Web Project Build Performance

ScottGu's Blog — Fri, 22 Sep 2006 19:06:56 GMT

This posts covers how to best optimize the build performance with Visual Studio 2005 and Visual Web Developer

Tip/Trick: Optimizing ASP.NET 2.0 Web Project Build Performance with VS 2005

ScottGu's Blog — Fri, 22 Sep 2006 21:47:52 GMT

This posts covers how to best optimize the build performance with Visual Studio 2005 when using web projects.

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

Joe — Mon, 25 Sep 2006 18:47:48 GMT

Chrsi,
You wrote:
"I did call support yesterday to get the fix myself, and it did take about 15 minutes. While this is not as quick as a web download, we've made every effort to make it quick and painless.

Let me know if you get a different experience when you call support."

I just called to get the Hot fix and it took 26 minutes. I was transferred on the phone 3 times. In all I had to speak with 4 reps. I gave the KB article numbers to the first rep and they were not passed on to the 2nd rep. I had to repeat them.

No one could tell me if SP1 was coming out this week or not. So I decided to get the hot fix now rather than wait.

Note: all of the reps were professional and courteous. The process itself is just time consuming.

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能

QPanda — Tue, 26 Sep 2006 05:00:36 GMT

ASP.NET, Visual Studio, Tips and Tricks

Scott Hanselman's Computer Zen - What's the upper limit on the number of projects within VS2005?

Wed, 27 Sep 2006 02:13:37 GMT

PingBack from http://www.hanselman.com/blog/WhatsTheUpperLimitOnTheNumberOfProjectsWithinVS2005.aspx

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能

qdzx2008 — Wed, 27 Sep 2006 20:45:24 GMT

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能

ASP.NET Chinese Blogs — Tue, 03 Oct 2006 20:48:03 GMT

【原文地址】Tip/Trick: Optimizing ASP.NET 2.0 Web Project Build Performance with VS 2005 【原文发表日期】Friday, September

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能

scottgu — Fri, 03 Nov 2006 11:18:54 GMT

这个帖子讨论在Visual Studio 2005中开发web项目时，如何优化其Build性能。如果你正受缓慢Build的煎熬，或者想知道怎么提高Build速度，请继续读下去。

re: Visual Basic perf fixes to issues with large VS2005 solutions / projects

nanu — Wed, 06 Dec 2006 14:51:19 GMT

hi,

i can't build a multiThreading project statically in VS2005 on Vista, whats the reason? if can't then what are all the dlls need to be copied to run the application in non-VS2005 installed system in Vista?

regards,

nanu

在VS 2005里优化ASP.NET 2.0Web项目的Build性能

ljianl — Sun, 25 Feb 2007 11:05:59 GMT

这个帖子讨论在Visual Studio 2005中开发web项目时，如何优化其Build性能。如果你正受缓慢Build的煎熬，或者想知道怎么提高Build速度，请继续读下去。

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能

克隆 — Fri, 02 Nov 2007 11:22:11 GMT

这个帖子讨论在Visual Studio 2005中开发web项目时，如何优化其Build性能。如果你正受缓慢Build的煎熬，或者想知道怎么提高Build速度，请继续读下去。

技巧和诀窍；在VS 2005里优化ASP.NET 2.0Web项目的Build性能(转)

幸福 — Wed, 21 May 2008 10:03:52 GMT

这个帖子讨论在VisualStudio2005中开发web项目时，如何优化其Build性能。如果你正受缓慢Build的煎熬，或者想知道怎么提高Build速度，请继续读下去。

VS2005网站...