35

In VS2012, my web project debugs fine like always. I use IIS Express. Today, I installed VS 2013 and when I press F5 to debug, I get

enter image description here

I can't find a solution to this anywhere. I tried clearing out temp files, change the port number from 7227 to something else, deleting iis express config files, etc. I even uninstalled and re installed VS 2013.

I can run without debugging, then attach to IISExpress and that works, but I can't start with an F5. Any clues?

EDIT: Happens on another machine as well with fresh install of windows 8.1 and VS 2013

EDIT: SOLUTION: I had Silverlight checked as a Debugger. I unchecked Silverlight and I was able to debug using Chrome or Firefox using F5. Obviously something isn't right here, but I don't need Silverlight debugging anyway.

ScottG
  • 10,711
  • 25
  • 82
  • 111

4 Answers4

40

I had this problem and it was caused by IE not being the default browser. You can correct this by following this answer

Visual Studio opens the default browser instead of Internet Explorer

Community
  • 1
  • 1
Kevin Ross
  • 7,185
  • 2
  • 21
  • 27
  • 5
    Wow, hours and hours wasted and just by setting the default to IE, it fixed it. However, I don't want to use IE..This is obviously a Visual Studio bug. Thanks for the answer. – ScottG Oct 21 '13 at 12:56
19

The answer was given by @ScottG in his edit, but here's a clearer explanation:

Open your Web Project Properties settings, click the Web tab, and under 'Debuggers,' unclick 'Silverlight.' Obviously, if you're needing to debug silverlight another solution will have to be found, until the VStudio team fixes this bug.

Nicholas Petersen
  • 9,104
  • 7
  • 59
  • 69
3

Undesirable workaround for a seemingly related problem (not an answer):

I created a new Silverlight project in VS2013 (express edition, C#) and got nearly the same error upon trying to run the application in debug mode (by pressing F5). The error message also ended with 'A null reference pointer was passed to the stub.'

I set my default browser to IE10 and now the debug mode for Silverlight applications in C# in VS 2013 (express edition) works fine.

ian.mcdavid
  • 31
  • 4
  • 1
    You don't necessarily have to have IE as your default; you can change the browser being used to debug in the debug toolbar. – Joe Oct 31 '13 at 17:52
  • Unfortunately, you do have to have IE as the default for Silverlight debugging. It does not work with any other browser as of VS 2013 RTM. – ScottG Oct 31 '13 at 19:18
  • With my VS2013, changing to IE using the Debug Toolbar works for me. Version 12.0.21005.1 REL. – Per Lundberg Jun 23 '14 at 11:02
0

I've just had the opposite problem, which the last post solved for me!

I've upgraded a Silverlight project from VS2010 to VS2013 (and I can confirm that if you've used a Domain Service you're in trouble; despite what Microsoft say, the project would NOT compile under 2013 and gave an error for EVERY edmx datatype, stored procedure etc!).

When I finally got it compiled after a day's slog (and no it's not backwards compatible, this is a 1-way upgrade), it ran, but behaved slightly differently. So I put in some breakpoints which it proceeded to completely ignore.

The Silverlight debugger needs to be checked but wasn't. I assumed it was part of the vbproj file? Have had no problems with the IE settings.

Ade

Ade
  • 96
  • 5