jerryjackson.net

I wish it was that simple. I’m once again working in the Microsoft realm doing .NET development. I’ve seen things happen in VS2005 which I clearly do not have the capacity to understand.

I’m part of a team that’s combining parts of other products/projects into a new stand-alone baseline product for our company. All the other previously existing products will become enhancements to this new baseline product.

Needless to say, the VS Solution file has plenty of stuff in it – many projects, references, etc.

Here’s the sequence of events I just witnessed while attempting to get a clean build after my last half-hour of code exorcism (removing all traces of the original products from this new one so it can truly stand alone without dependency on the others):

• clean
• rebuild
• clean
• rebuild (don’t ask me why I’m starting to think this multi-rebuild process is “normal”)
• lots of errors
• clean
• rebuild
• fewer errors
• clean
• rebuild
• fewer errors
• clean
• rebuild
• more errors
• wait and watch the “live” errors list (VS2005 is apparently doing something behind the scenes here)
• wait some more (I was actually distracted doing something else when my peripheral vision picked up the changing errors listing)
• errors start disappearing off the list
• finally they’re gone
• can it be? do I really have a clean build?
• clean
• rebuild
• more errors
• clean
• rebuild
• NO ERRORS (but I don’t really believe it)
• clean
• rebuild
• no errors
• again
• no errors(now I believe it – sort of)
• QUICK – check it all in to VSS
• spend the next 5 minutes trying to make the voices stop

It should be noted that at no point during that sequence was any file edited or saved!

Looking forward to deploying this monster….