My client recently asked me to remove a part of a huge CRM web application I've been developing. Removing this piece (another project that is referenced by my web application), means that almost every method & function throughout the entire program will have to be updated. With around thousands of them, you can imagine it will be time consuming.

Removing the reference to the project that I had included means, for VB, that it should then show compile/build errors everywhere that it is referencing the project that is now gone.

That doesn't happen! Visual Basic will only show one or two errors, or none at all, but the build fails. I can apparently only show the errors if I actually look at every single .vb file and wait about 15 seconds, one by one, but that causes it to claim that none of the objects on the webform exist until I view the webform, too, close the .vb file, and re-open it! No matter how many times I restart or rebuild the web application, it will only show one, or two, errors. It picks them randomly from all over the site, and once I correct them I have to build again for it to pick up another two from somewhere else throughout the site. It is taking so long I'm close to telling the client to live with the other part of it. At this rate, to fix thousands of them will take me weeks.

What can I do to make ALL of the errors show up at once?