SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Not sure how much sense that title makes, but the issue that I am running into is that when I begin debugging a project (XYZ) a page from a completely different project (ABC), that is in a different solution will pop up when it hits an exception.

These are two totally different projects that contain custom code that is being run against the same SharePoint instance. I took a screen shot of what is going on:

enter image description here

The tab that is selected has popped up and thrown a null reference exception, but if you look in my solution explorer you will see that this file does not exist there. Why would something like this happen?

share|improve this question
up vote 1 down vote accepted

By default when debugging Visual Studio will stop on User-Unhandled Exceptions

share|improve this answer
I would add Ctrl-Alt-E normally brings up the dialog for controlling what exceptions Visual Studio breaks on, and in what conditions. I find breaking on any thrown exception can be useful during development/debugging. – Andy Burns May 21 '12 at 10:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.