VS 2005 Compiler Performance (Web Site Project)

[Guest]

Have a web site project with only a few pages. The site is in a solution that
has about 20 projects that are business objects that the site is dependent
on. When I do a build the compiler says "Build succeeded" in about 5 seconds
but then the screen is frozen for about 40 or more seconds after that. The
solution explorer and other IDE parts go blank and redraw during that time.
What is happening during the 40 seconds after the build and how can I make it
faster? Have used VS2003 for years with larger projects and have not had
this kind of problem. This slowness will prevent us from moving our main app
to VS 2005.

 

[Frans Bouma [C# MVP]]

Have a web site project with only a few pages. The site is in a
solution that has about 20 projects that are business objects that
the site is dependent on. When I do a build the compiler says "Build
succeeded" in about 5 seconds but then the screen is frozen for about
40 or more seconds after that. The solution explorer and other IDE
parts go blank and redraw during that time. What is happening during
the 40 seconds after the build and how can I make it faster? Have
used VS2003 for years with larger projects and have not had this kind
of problem. This slowness will prevent us from moving our main app to
VS 2005.

Chop up your solution into smaller solutions and reference the
assemblies in binary form. 10 to 1 you aren't working on all 20
projects at a time.

So your webproject solution should just contain the webproject and
perhaps the few projects it directly works with.

Also use a web application project and not the original website
project. Both are pretty sucky, but the web application project is more
efficient. web application project was a project form introduced as an
add-on to vs.net 2005 and installed with vs.net 2005 sp1 (which you
should install anyway).

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

 

[Guest]

Chop up your solution into smaller solutions and reference the
assemblies in binary form. 10 to 1 you aren't working on all 20
projects at a time.

So your webproject solution should just contain the webproject and
perhaps the few projects it directly works with.

Also use a web application project and not the original website
project. Both are pretty sucky, but the web application project is more
efficient. web application project was a project form introduced as an
add-on to vs.net 2005 and installed with vs.net 2005 sp1 (which you
should install anyway).

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)

 

[Guest]

Thanks for the reply.

I posted a message similar to the following yesterday but everything I typed
was truncated from the message. So apparently there is a bug in the newsgroup
posting:

I tried converting from web site to web application, it didn't seem to help.
This isn't going to work out anyway since I am now using some vendor
templates that don't seem to support web application.

Hopefully I don't have to break up the project. We tried to break it up
before and had a lot of problems with dependencies and file locking. Also I
find it very hard to just resign myself to VS2005 web projects are "sucky"
and worse performing than the original version of VS .NET. If I have to break
up the project then there isn't any value proposition to upgrading to later
versions. There must be some optional new feature that is wasting all my time
after a build.