Running Team Edition for Software Developers version 8.0.50727.181 (QFE.050727-1800).
I have the following VS.NET hotfixes installed:
KB917452 and KB920805
I have the following .NET Framework 2.0 hotfixes installed:
KB917452, KB916002 and KB917283
Until recently, I also had hotfix KB922981 installed (couldn’t find a link for this one).
All the hotfixes are required by my primary client.
My development system has NOTHING on it except Visual Studio, Vault and VPN (CheckPoint) software.
Last Friday (September 1), the lead developer for the client emailed all the devs and said they needed to uninstall KB922981 and reinstall KB916002 which I did. He advised us to reboot after the uninstall and then again after the reinstall of KB916002. So, uninstall KB922981, reboot, reinstall KB916002, done.
I did this late on Friday so I wouldn’t forget after the long holiday weekend.
Tuesday rolls around and I’m ready to get back to work, so I log into my dev workstation and run a clean-up script (again, from the client) which deletes ASP.NET temp files, restarts IIS, etc. I did a “Get Latest” from Vault, fired up the solution (which, BTW contains 97 projects) and issued a “Rebulid Solution”. A few minutes later, I notice the build failed.
The build error:
Error 1 Type ‘ErrorMessageManager’ is not defined. C:\
Looks simple enough, right? I opened that particular file and looked at the offending line.
Private _ErrorMessages As IErrorMessageManager = New ErrorMessageManager()Wanting to move on as quickly as possible, I simply right-clicked on “ErrorMessageManager” and selected “Go to definition.” I was now looking at the ErrorMessageManager class. Hmmm….if it’s not defined, why could I jump to it. I must be missing something, so exit VS, back to Vault, “Get Latest”. No new files were found. Cool. Checked references…no problems.
Back to VS. This time I did a “Clean Solution” and then a “Rebuild”. Same error. Jumped on IM and asked another dev if they had any issues. Nope, just me. WTF?
I decided to reboot the system again, just for the hell of it. C’mon…it’s Windows and VS 2005. Maybe a reboot would help.
Nope.
I composed an email to the other devs in the company I’m sub-contracting for. Noone else had any issues, even after following the same steps I did.
Ok, time to get tough. After ensuring I had no files checked-out, I completed deleted my source tree, ran the clean-up script again, “Get Latest”, clean solution, rebuild. Same freakin’ problem.
Ok, maybe it’s the hardware (I know…grasping a bit, but WTF). I ran a chkdsk /f. No issues. I defragged.
By this time I was really getting pissed off. The owner of the company I’m sub’ing for:
Can I assume that you havea) stopped the IIS processes
b) removed ALL temporary files underneath c:\windows\micorosoft.net\v2.x\temporary files\
c) deleted the c:\
d) rebooted
e) get latest of both web and enterprise
f) recompile all
Yep, did all that, in that order too.
So, now it’s Friday and I’m still having this problem. I’ve run diagnostics on my dev workstation and everything is good-to-go.
Maybe you can find something that leads you to the problem if you take a look at the output generated during the building process. Try setting Tools\Options\Projects and solutions\Build and run\MSBuild project build output verbosity = diagnostic.
D2F:
Thanks for the suggestion.
I set the build output verbosity to diagnostic, but it didn’t provide any more insight into this particular error.
I see this in the build output:.
.Web/PhotoUpload/controls/’.
Building directory ‘/
C:\\
\trunk\.
.Web\PhotoUpload\controls\Copy.ascx.vb(13,0): error BC30002: Type ‘ErrorMessageManager’ is not defined.
Validation Complete
and then it moves on to the next project.