I have a growing WSP (via FPSE to an IIS 6.0 development server) that dependends upon a class library in the same solution (project reference). There are multiple developers working on the WSP, albeit in separate directories.I am the project leader (and I am responsible for the class library), so I perform periodic rebuilds in order to verify site consistency as a whole. I have noticed that a web site rebuild does not always get the latest versions of the ASP.NET files from IIS; rebuild solution seems to fare marginally better.Also, I ran into a sitiuation in which neither rebuild option would publish the class library, even though it is set to refresh. I suspect that this was because another developer somehow touched the refresh file, but the only way I could get it to refresh was to delete the contents from bin and try again. There was nothing to indicate that the update had or had not happened (the message regarding the upload in the status bar isn't up for very long - maybe the refresh status could be dumped to output even when no refresh occurs or when it is successful?), so the only way I noticed this issue was because I was getting errors regarding newly added classes. FYI, removing the reference via the property pages caused VS 2005 SP1 to crash.Thomas S. Trias