K
Ken Kolda
If the two classes are in different assemblies, then there's a chance that
the program is running against a cached copy of the assembly than the one in
the debugger (I've seen this many times). When the debugger starts up, check
the Output window and see where it loaded the DLLs from. In my case, it was
sometime loading them from Docs & Settings\Local Settings\assembly instead
of from the project folder.
Ken
the program is running against a cached copy of the assembly than the one in
the debugger (I've seen this many times). When the debugger starts up, check
the Output window and see where it loaded the DLLs from. In my case, it was
sometime loading them from Docs & Settings\Local Settings\assembly instead
of from the project folder.
Ken