I was doing some refactoring of my project, rearranging the projects and such. That is a joy as always. I had it all rearranged, no errors, it compiled and everything and then added a few existing files from a test project. BOOM. 44 ListPopulating event handlers are now reporting errors. In all cases they report (method name differs, but other than that they are the same):







Now unless I'm going blind, those signatures sure look the same to me. Any ideas what might be going on? I'm stuck until this gets fixed.



Thanks!

OK, a bit more info. I used msbuild from the command line to build the solution. It succeeded with no errors. ...Sigh... So really, the issue is how to get VS to stop having a tizzy fit over nothing. Anyone else have unruly children?

Haha, would you believe that we're having the exact same problem right now with the exact same event handler?  It's only happending with our Infragistics wrapper combo box right now, and it's only happening on Trent's computer.  Everyone else's works fine!!  We've tried everything from dumping the solution folder and getting the latest version clean from source control to removing all of the assemblies from the GAC.  Bah, hopefully stuff like this will get fixed in VS2008 (though I won't hope too much for fear of being let down).

I'll let you know if we find anything.

It's good to know I'm not the only one. I'm going to try and revert to a previous version from my repository and just redo the edits (which works cause I'm the only one developing it right now)....and pray.



I also hope that 2008 fixes some of this garbage...but I'm not counting on it.



Thanks for keeping me updated, I do likewise.



I think my initial assessment was right...gremlins

I got mine fixed. It was related to references. I was moving around classes first, then setting references when I found errors. When I did this with the Microfour.StrataFrame.UI assembly after adding the classes (as soon as it was added) I'd get the compile errors. When I made sure all the references were set first, then added the classes, no problems.



Of course, I had the freedom to revert to a previous revision. I doubt you have that freedom. But maybe this info will spark a brilliant thought on your end!

Yep, we're going to try removing and re-adding the references again on our end as well.  For the time being, we just commented out the errors because they were on non-essential forms and we wanted to continue making progress.  So, when we go back to working with those forms, we'll be re-addressing the problem, at which time, we'll play with the references some more.

This happened to me again. This time I had set the references, so either that had nothing to do with it...or there are more than one ways this can break. Did you ever resolve this? If so, how? Does VS 2008 help with this?



Thanks!

This is more of a .NET and designer related issue versus an SF issue.  However, since we have been on 2008 we have not experienced this.  But that could just be coincidental

Yep, I realize this is a .net issue. I just opened the solution in VS2008 and there is no problem...so I guess I'm using VS2008 now! Bloody VS...Long live VS!

LOL...funny how that works, huh?