Comments on: Performance of Visual Basic 2008 http://ardentdev.com/performance-of-visual-basic-2008/ For the Love of Code Sat, 12 May 2012 12:47:01 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Rob Collett http://ardentdev.com/performance-of-visual-basic-2008/comment-page-1/#comment-23436 Rob Collett Sat, 05 Apr 2008 18:36:47 +0000 http://www.ardentdev.com/blog/index.php/2008/01/08/performance-of-visual-basic-2008/#comment-23436 turn off 'Generate XML documentation' in your project options. Speeds up the ide greatly. turn off ‘Generate XML documentation’ in your project options.
Speeds up the ide greatly.

]]> By: Đonny http://ardentdev.com/performance-of-visual-basic-2008/comment-page-1/#comment-14840 Đonny Fri, 01 Feb 2008 21:45:47 +0000 http://www.ardentdev.com/blog/index.php/2008/01/08/performance-of-visual-basic-2008/#comment-14840 I strongly disagree with the table. I have solution with more than 100 VB files. Build takes more than 3 minutes. After pressing enter at end of the line, Visual Studio is not responding for up to 30secs. I can't work this way! I strongly disagree with the table.
I have solution with more than 100 VB files. Build takes more than 3 minutes. After pressing enter at end of the line, Visual Studio is not responding for up to 30secs. I can’t work this way!

]]> By: Robert S. Robbins http://ardentdev.com/performance-of-visual-basic-2008/comment-page-1/#comment-11290 Robert S. Robbins Wed, 09 Jan 2008 17:30:02 +0000 http://www.ardentdev.com/blog/index.php/2008/01/08/performance-of-visual-basic-2008/#comment-11290 Your performance will be lousy once the msiexec.exe process begins to run mysteriously after installing Visual Studio 2008. It will even hog the CPU when you run Visual Studio 2005. I suspect it is trying to repair something related to the .NET Framework 2.0. Running Visual Studio in safe mode does not help. Your performance will be lousy once the msiexec.exe process begins to run mysteriously after installing Visual Studio 2008. It will even hog the CPU when you run Visual Studio 2005. I suspect it is trying to repair something related to the .NET Framework 2.0. Running Visual Studio in safe mode does not help.

]]>