Sorry for not getting back to you earlier on this!
I'm afraid I can't help you directly on this. Here are some things you
1) If you have some kind of a particular project (database project?
test project?) in your solution, you may try to temporarily remove it
from the solution to see if it's related to it. If you look at the
output window, you should see what PageMethods is doing. At some point
the add-in writes something like 'Processing "SomeProject"'. This
should help you to define the project PageMethods chokes on.
2) You can open the PageMethods solution in Visual Studio, and debug
the add-in by running another instance of Visual Studio with
PageMethods activated and attaching the first instance to the second
one in order to debug the add-in. This can also be achieved by running
the add-in in debug mode, as soon as devenv.exe is specified as the
program to run.
3) You can recompile the PageMethods add-in and add a try..catch block
around the code where the exception is raised. This is in Addin
\Processor.cs, line 395: foreach (CodeElement element in
codeModel.CodeElements) ProcessCodeElement(element, url);
Apparently the CodeElements property can't be accessed for one of your
If you are still investigating this and find a solution, please share
it with us here.
It's too bad Visual Studio makes it difficult like this. Who doesn't
hate COM and its very informative "Catastrophic failure"s?!