Skip to main content
Home Forums Silverlight Programming Programming with .NET - General Debug ERROR ! : "The break point currently will not be hit , no symbols have been loaded to this document"
20 replies. Latest Post by lgranata on October 8, 2009.
(0)
Epsilone3
Member
248 points
138 Posts
09-28-2007 10:54 PM |
"The break point currently will not be hit , no symbols have been loaded to this document"
This is just unbleiveable problem , The symbols don't loaded cause ???.
I've got combine project ,
With ASP + 2 SilverLight project .
Both of the SilverLight Project's link to the ASP with the option <Add silverlight link>
But the break point don't stop 90% of the time.
I read somewhere that it could be connected to the synchronize delay of the *.pdb building files.
Any suggestions !!.
sakthisa...
336 points
09-30-2007 10:42 PM |
Hi,
One reason could be that the reference is not proper. You may have given a reference to the dll whose source is changed later.
Eg. There are two projects ProjA and ProjB. ProjB is added as a reference to ProjA. But, Instead of adding reference as a project, you browse the dll path and add the reference(this dll path is not the Visual studio project bin path).
So, I think you have added the silverlight link from another location instead of the location where the solution project is present.
Regards,
Sakthi
10-01-2007 5:53 AM |
Hi 10x.
I've got ASP project that hold under two silverlight project .
The SilverLight project connect to the ASP project with the option <Add silverlight link>
So this option automatically update & upload the *.dll and the source files of the SilverLight projects into the ASP project.
I think the It could be the synchronize time of the *.pdb files.
Or the building <action> setup .
Is there a reference somewhere of what exactly doing everyone of the building option :
Building action :SilverLight page ..and so..on..
But I by pass this problem for now !
By creating anew project and add with copy paste the code into a new template of new files.
But It's problem really annoyed and return frequency.
10x alot.
Guy.
luisabreu
Participant
1676 points
612 Posts
10-01-2007 7:05 PM |
hello.
are you trying to debug silverlight code from your asp.net project? if so, don't forget to enable the silverlight debug option in your web project options.
10-02-2007 1:46 AM |
No I put the break-point in the original project.
Please check my project over here :
http://silverlight.net/forums/t/5278.aspx
The problem change to something little relse.
But it's on the same breakpoint problem bases.
Filipus
20 points
13 Posts
02-28-2008 9:56 PM |
I have got the same problem :( I am using ASP.NET future with 2 silverlight projects in the same solution. And sometimes when I want to debug a silverlight code behind, the running version is not the same like in my solution. Then it tells me that my breakpoint will not be hit. I have tried to delete DEBUG, delete the copied xaml page, delete nearly everything. But still the same.
Before it happened just sometimes, but right know, I am not able to do any change in my code. If i run the solution, it always runs the same old version. I am really desperate right now.
If anybody know how to solve this, please let me know. I have tried googling, but nothing :(
Thanks Filip
jamesthu...
3 points
3 Posts
04-04-2008 10:48 AM |
I had this same problem... managed to fix it by going into my Temporary Internet Files, finding the XAP file for my project and deleting it.
James.
helfon
48 points
34 Posts
04-04-2008 5:50 PM |
I have this exact same problem. In my case it is due to IE7 caching. Whenever I see it happen I go Tools -> Internet Options and under Browsing History hit Delete and then Delete Files. I believe this causes it to redownload the dll.
Montago
265 points
190 Posts
04-24-2008 4:36 AM |
When you add a Silverlight project to a asp.net solution, you create 2 projects...
A. the startup project (interface starter)
B. the interface itself
1. right click on the startup project (SilverlightWeb --- the one with default.aspx in it )...
2. click on 'Property Pages'
3. open 'Start Options' Tab
4. enable Silverlight Debugger
5. OK
this was the solution for me
kaladar
8 points
8 Posts
06-02-2008 4:19 PM |
What I did to restore breakpoints on my Silverlight Project is to remove the link to my silverlight app from my silverlight host and then add it again, this seem to fix it.
fastduck...
31 points
23 Posts
06-03-2008 6:27 AM |
thanks helfon. i was having the same problem too. deleting the IE cached fixed it.
SteveWong
Contributor
6323 points
1,281 Posts
06-03-2008 7:04 AM |
I got this problem before. But actually,
I solve it by entering http://localhost/.... instead of http://127.0.0.1/...
I dont know if this affect the debug of the project
If I make anything wrong, please do tell me.
kbatyai
4 points
08-13-2008 4:30 AM |
Ah...
I had the same problem.
It can be fixed by deleting the SilverlightApp reference on the WebProject property page, and ReAdd it :)
S*x
KRis
theotherjay
08-15-2008 10:57 AM |
I had a similar problem. My breakpoints were said to not be hit, and when I debugged my application, it threw an error on the IE page referring to a line of code that had been removed. The only way I was able to fix the problem was to delete my temporary internet files. Visual studio should be smarter than this.
This has never happend before I installed sp1 for vs2008. Is this a known issue?
Slacquer
2 points
2 Posts
04-16-2009 7:30 PM |
Hello, for what it's worth, I had a similar (or maybe the same) problem, I noticed that for whatever reason Visual Studio had disabled the DEBUG Silverlight checkbox.
In the web projects property pages, the web tab, scroll to bottom and check the Silverlight (and sql for me) check boxes, then all was well.
Hope it helps...
omer.javed
07-14-2009 4:06 AM |
Yup it worked! Thanks Montago.
danielkward
33 points
7 Posts
07-16-2009 5:26 PM |
After upgrading my SL3 Beta Projects to SL3 RTW I experienced this issue, only with SL2 upgrades though, all new SL3 work as they should. Jim McCurdy saved my head on this one, the link is below but the short end is remove the <Deployment.ApplicationIdentity> tag from your AppManifest.xml file in the silverlight project and voila, time to get back to work.
http://timheuer.com/blog/archive/2009/07/10/silverlight-3-released-what-is-new-and-changed.aspx
Jugdesh
18 points
07-29-2009 12:16 AM |
Hey mine were solved by right clicking on web project going into [Debug] Menu and then clicking [Start a new Instance].
asifmaniar
08-13-2009 3:26 PM |
Make sure you clear your browser cache.
rajkra
10-01-2009 7:16 AM |
Thanks Slacquer! Yup! it really worked for me! :)
lgranata
10-08-2009 10:38 AM |
That worked for me too, thanks