VS2005 Build Speed

Oh My God, VS-2005's build speed sucks, my solution takes 30 seconds to build from the command line via msbuild. It takes a 2:55 to build in VS!!

Solution is only 15 projects on a completely fresh install of XP+VS, no A/V nothing else at all.  3 of these projects are web projects, and it's these that take the time, at least 95% of it.

Not pleased.

Stephen.

A) what are you compiling?
and
B) how fast is your computer?

If you're trying to use VS2005 on a 486, expect long build times.  Or, if you're building 100k lines of code, it will take a while.

VS2005 uses MSBuild. If it can be fast on commandline, it should be within VS2005, too. But it isnt.

Tried this on two machines,  one is is a 3GHz P4 with 2Gb of RAM and FAST SATA drives, the other is a Laptop, 2GHz P4 1Gb or RAM 7200RPM hard disk.  The build times are within seconds of eachother.  The projects are all C# generating about 1.22Mb of final assemblies (in debug) + 2.7Mb of PDB's.  Quite a small project really.

And don't even bother turning the accessability checks on, its been sitting there, checking the site for over 10 minutes now!!

Stephen.

Yeh I've noticed the build speed is worse than on VS2003...

same here, Build speed sucks lol:(

try disabling your antivirus program, it makes it faster

no antivirus on this machine

Stephen.

Hmm, something must be terribly wrong if the build time of your website takes 10 minutes. I have a solution of 14 projects and it compiles in about 2 minutes.
This includes two webprojects (one webservice + one webclient).

I hope you didn't have VS2005 betas installed before you installed the final release. Because this can cause major headaches when it comes to compiling.

WillemM wrote:

Hmm, something must be terribly wrong if the build time of your website takes 10 minutes. I have a solution of 14 projects and it compiles in about 2 minutes.
This includes two webprojects (one webservice + one webclient).

In VS2003, I've got a Solution comprised of 4 class libraries, one desktop app, and 2 wep-applications (one web-service, another asp.net website), it takes about 4 seconds to build.

WillemM wrote:

Hmm, something must be terribly wrong if the build time of your website takes 10 minutes. I have a solution of 14 projects and it compiles in about 2 minutes.
This includes two webprojects (one webservice + one webclient).

I hope you didn't have VS2005 betas installed before you installed the final release. Because this can cause major headaches when it comes to compiling.

If you had read the original message you would have seen 'completely fresh install of XP+VS, no A/V nothing else at all'

Anyway the ten minutes is only when the WCAG validation is enabled.  A standard build takes much less, only about 5 minutes...

In my case two of the projects are web user control (ascx) libraries that have to be built + deployed (smart move removing direct refs for web projects, not!) and the other is the main web app + plus a load of standard c# lib projects.

Stephen

W3bbo wrote:

WillemM wrote: Hmm, something must be terribly wrong if the build time of your website takes 10 minutes. I have a solution of 14 projects and it compiles in about 2 minutes. This includes two webprojects (one webservice + one webclient).

In VS2003, I've got a Solution comprised of 4 class libraries, one desktop app, and 2 wep-applications (one web-service, another asp.net website), it takes about 4 seconds to build.

This took about 30 secounds in 2003, before I 'upgraded' to 2005. 

Stephen.

blowdart wrote:

Switch the verbosity to diagnostic.

There's a summary at the end which breaks down time in tasks, and the internal workings.

Compare, see if all the timings are increased, or if only certain tasks are lagging.

This is almost funny, but you change the build options in 'Options->Build And Run' to detail or diagnostic and there is NO extra logging in the output window for web projects, i.e. the ones I have issue with!!

Visual Studio wrote:

Target "Rebuild" in file "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets"
Building target "Rebuild" completely.
No input files were specified.
Done building target "Rebuild" in project "GrosvenorTechnology.csproj".
Done building project "GrosvenorTechnology.csproj".
Build succeeded.
Time Elapsed 00:00:01.27
------ Rebuild All started: Project: http://localhost/Perfectphase.Security.Web/, Configuration: Debug .NET ------
Validating Web Site
Building directory '/Perfectphase.Security.Web/App_Code/'.
Building directory '/Perfectphase.Security.Web/Controls/Security/'.
Building directory '/Perfectphase.Security.Web/UserAdmin/Secure/'.
Building directory '/Perfectphase.Security.Web/'.
Building directory '/Perfectphase.Security.Web/UserAdmin/'.
Validation Complete
------ Rebuild All started: Project: http://localhost/GrosvenorTechnology.Web.Documents/, Configuration: Debug .NET ------
Validating Web Site
Building directory '/GrosvenorTechnology.Web.Documents/App_Code/'.
Building directory '/GrosvenorTechnology.Web.Documents/Controls/Documents/'.
Building directory '/GrosvenorTechnology.Web.Documents/Documents/'.
Validation Complete
------ Rebuild All started: Project: GrosvenorTechnology.Schema.UPS.TrackResponse, Configuration: Debug Any CPU ------
Build started 14/11/2005 01:44:20.
Initial Properties:
_DebugSymbolsProduced = true
_DeploymentApplicationManifestIdentity = Native.GrosvenorTechnology.Schema.UPS.TrackResponse
_DeploymentBuiltUpdateInterval = 0
_DeploymentBuiltUpdateIntervalUnits = Days
_DeploymentDeployManifestIdentity = GrosvenorTechnology.Schema.UPS.TrackResponse.application
_DeploymentFileMappingExtensio

EDIT: if I build from the comand line I get the info you mentioned, but I don't have issue with the comand line msbuild speed, it's the fact that VS takes much much longer

Stephen