[SOLVED - SORTA] Silverlight app won't stop at breakpoints

Question

0.00/5 (No votes)

See more:

, +

Instead of getting the red circle, I get the hollow circle with an exclamation point icon, and when hovered, it says:

This breakpoint will not currently be hit. No symbols have been loaded for this document.

I've tried shutting everything down, deleting the bin and obj folders, and even restarting the machine, and nothing appears to have a positive affect.

Does anyone have any other ideas?

EDIT =============

And to head this off before the less observant of you say anything, yes - I checked google before asking.

SOLUTION ============

Ever since this project was started, I've been able to debug it without any problems. Today, I had to set the Silverlight app itself as the startup app. Prior to today, it was working with the web page as the startup project. I don't know what's changed, because I haven't added a new file in WEEKS.

Posted 18-Mar-11 5:40am

#realJSOP

Updated 18-Mar-11 9:19am

v4

Add a Solution

Comments

Uday P.Singh 6-Dec-11 12:59pm

Have your problem solved? If yes, then how? can you share it with us?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Yusuf · Answer 1 · 2011-03-18T05:52:00

Solution 1

John, I am really disappointed. Aren't you who scold people for not harnessing the power of google. See what I found using your own words[^]:

http://social.msdn.microsoft.com/Forums/en/vssetup/thread/000cefdc-369c-421d-8e23-8c4e7c312ee1[^]

Posted 18-Mar-11 5:52am

Yusuf

Comments

#realJSOP 18-Mar-11 11:54am

I saw that, and it doesn't apply (and neither do the links they provided). I followed all of the advice I found on the subject (delete folders, shut everything down, blah blah), and that didn't help either.

To throw it back at you, I'm surprised that you would think I wouldn't check google before posting a question here.

Yusuf 18-Mar-11 12:04pm

Well, you stated "everything", which is catch-all phrase, it seems you have tried this
http://geekswithblogs.net/dbutscher/archive/2007/06/26/113472.aspx

but have you tried this
http://boxbinary.com/2010/04/debugging-silverlight-in-visual-studio-breakpoints-not-being-hit/

#realJSOP 18-Mar-11 14:36pm

Actually, I said I shut everything down, deleted bin and obj folders, and then when that didn't work, restarted the machine.

Sandeep Mewara · Answer 2 · 2011-03-18T07:12:00

Solution 2

By any chance can this be it?:
Unable to DEBUG Silverlight project?[^]

Might be the Silverlight debugging is off, but I doubt it as you surely must have checked that in the first place.

Posted 18-Mar-11 7:12am

Sandeep Mewara

Comments

#realJSOP 18-Mar-11 14:35pm

Everything is fine in Properties. I was degugging it just fine yesterday. The only thing I did between shutting the IDE dow yesterday, and starting it today was log off my machine at the end of the work day, and log back on this morning.

Sandeep Mewara 18-Mar-11 15:25pm

Just some thoughts:

Cleared cache and temporary internet files and ASP.NET temporary files folders?
But that would be needed if you have configured to use IIS instead of VS in-built server.