My migration from 2003 to 2005 had the same issues. What I did to resolve
my issues:
1. Execute "Clean Solution" on all my solutions.
2. Removed all references to my DLLs
3. Added the references I removed in step 2 above as "Projects" not DLL
references
4. ran a Clean solution again
5. verified all my build dependancy and build order - in some cases I had
circular build dependancy, not good - so I had to partition out to new
projects/namespace and adjust code references accordingly - also some
projects did not have the build dependancy set correctly
6. Build all my solutions
I have multiple core projects/dll's I use in many solutions so I did the
same process for each solution. It was time consuming (took about a 1/2
day) but now everything builds quickly, and works correctly. Even my web
applications compile quickly now. I have inheritance usage also, but I
don't think that is relevant to the cause of the super slow compiles. I
also have web references, but again, that doesn't seem to be involved
either.
You may not need all these steps and your mileage will vary. Unfortunately
the steps above are more a blanket solution rather than knowing exactly what
went wrong with the migration from 2003 to 2005 -- but it could take me
weeks to discover the real issue, vs. 1/2 day to force a blanket solution.
Best of luck and your not alone, I know several other developers that have
run into exactly the same problem.
"Dan Munk" <da*****@gmail.com> wrote in message
news:11**********************@u72g2000cwu.googlegr oups.com...
Hello,
I have a large project exclusively made up of interfaces (several
hundred) that define the business objects used in our system. Heavy
inheritance and aggregation are used in the project. In Visual Studio
2003 the project takes ~30 seconds to build. In Visual Studio 2005 the
project takes ~24 minutes. The project references one other assembly.
I've tried to reference the dependency both as a dll and as a project..
Has anyone else had a similar experience?
Thanks,
Dan
