System.MissingMethodException when method is there

  • Thread starter Thread starter Jape
  • Start date Start date
J

Jape

I have an db interface which my project (and several ther projects)
uses. Lets call it IF. Every time a certain type of project is made it
uses it's own db interface IF. Last time I made changes to the
interface in the beginning of 2009 without any problems. Now I added 2
new methods to IF and I'm getting the System.MissingMethodException
error on the new project and also on all the older ones. And the
methods are there that's not the problem. The same code works fine on
my development computer, but not in production server. I've tried (re)
building the IF and ALL related project on XP SP3, XP SP2, and 2003
Server. The productions server is W2k3. I have built the on debug,
release again and again but no luck... I'm starting to suspect the
problem is in some Windows Update, framework or maybe even security.

Please if you have any kind of idea how this might be resolved, answer
me. Thanks.
 
I'd use the assembly log viewer to see what assembly is actually being
loaded. You might be picking one up from the GAC because it's searched
first. Interface changes often warrant assembly name changes (assembly
version, strong name) to properly identify a difference because otherwise
you have a bunch of assemblies out there that are all named identically but
offer different interfaces.
 
I'd use the assembly log viewer to see what assembly is actually being
loaded. You might be picking one up from the GAC because it's searched
first. Interface changes often warrant assembly name changes (assembly
version, strong name) to properly identify a difference because otherwise
you have a bunch of assemblies out there that are all named identically but
offer different interfaces.
Click to expand...

Phil, thank you for the answer. I'll try your solution and get back to
you.
 
Ok, I used the log viewer and it seems that the correct asseblies are
loaded. I changed the version number just to be sure. I also (again)
tried to remove the added methods, clean solution, clean projects,
rebuild with release and debug, but the same MissingMethodException -
error still occurs. I found an older version of the dll, decompiled it
with reflector and even tried it after build and you guessed it,
MissingMethodException... If you Phil, or anyone else, have any other
ideas please share them. Thanks.
 
Problem solved. Other coder had changed the custom errorhandler and
that generated the MissingMethodException. The error was actually
something else, but the handler had a bug... Anyway thanks Phil for
your assistance.
 
Back
Top