bobbyjosephg
 Nuke Pro Posts:82

 |
| 01/24/2008 10:09 AM |
|
hi When i try to debug a module and insert a break point a warning message shows the the breakpoint will not currently be hit.No symbols loaded for this document. Any Idea how to resolve this
Thanks in advance \ Bobby |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/24/2008 10:27 AM |
|
I've not encountered this problem. Does the site build?
I assume that you are trying to insert a breakpoint in a codebehind file. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
bobbyjosephg
 Nuke Pro Posts:82

 |
| 01/24/2008 11:30 AM |
|
hi Yes the site builds and there is no other error . i am trying to insert a breakpoint in the codebehind.
i tried all the steps in the forums but still no remedy
regards Bobby |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/25/2008 9:35 AM |
|
Just to touch all bases: you do have debugging turned on, right? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
digmike
 Nuke Ace Posts:42

 |
| 01/25/2008 10:45 AM |
|
Hi, Are you sure the module dll file is making it's way into the dnn bin folder? Thanks, Mike
|
|
 |
|
|
Scippy One
 Nuke Newbie Posts:4

 |
| 01/27/2008 5:20 AM |
|
I've the same problem. The step I've followed are this:
- Download your chosen module (both Private Assembly & Source Code)
- Install Private Assembly version via Host -> Module Definitions -> Upload New Module
- Extract the Source Code into a separate folder under desktop modules (e.g. LinkSource for the links module source)
- Update the module definitions of the module (Host -> Module Definitions) by modifying each control and change the source to point to your newly created source folder. Each control must point at its equivalent.
- Load up your project and start debugging!
But it don't work likewise! |
|
|
|
|
bobbyjosephg
 Nuke Pro Posts:82

 |
| 01/27/2008 5:10 PM |
|
Hi Joe, Debugging has been turned on.Now as Mike has said, suppose I create a module with the name Department should there be a DLL in the bin folder?Currently there is no DLL of any of the modules that I have created.Is that a Problem. Regarding Scippy's post I tried the steps but it did not work for me.
Thanks Bobby |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/27/2008 10:45 PM |
|
No, there won't be a DLL until you create one. And, you don't have to create one.
When you say that you have "created" a module, exactly what do you do? Do you have a directory under Desktop Modules that includes your ascx and other files? Can you install the module onto a page in your developmental DotNetNuke environment?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
bobbyjosephg
 Nuke Pro Posts:82

 |
| 01/27/2008 11:09 PM |
|
Hi Joe, I shall explain what I did in detail.
1. I used the install version of DNN and installed a new site. 2. I opened the new site in VS 2005 . 3. I right clicked on the website and from the addnew I created a new C# module. 4. Then I inserted the necessary code. 5. After this I went to the module definitions and added a control. 6. Then I placed this module on one of the pages.
The module works correctly.But if a put a break point in the code and try to debug, a hollow circle with a warning symbol appears to the left of the breakpoint an whne the mouse pointer is placed on top of this it shows a message.
"The breakpoint will not currently be hit.No symbols loaded for this document."
Thanks Bobby
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/28/2008 8:13 AM |
|
You've got me ...
I'm assuming that it doesn't matter where you place the breakpoint. And, I'm assuming that you put the breakpoint in your .cs file, not in the .ascx file. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
bobbyjosephg
 Nuke Pro Posts:82

 |
| 01/31/2008 11:19 PM |
|
Hi Joe I have put the breakpoint in the cs file.
Thanks Bobby |
|
|
|
|
raul
 Nuke Newbie Posts:1

 |
| 01/30/2009 12:04 PM |
|
I'm in the same case. But my module is in VB.
|
|
|
|
|
bobbyjosephg
 Nuke Pro Posts:82

 |
| 02/01/2009 11:05 PM |
|
To Resolve this issue What i did was 1. I hosted the site locally on to my site. 2. In Visual studio click open website and change the seclection to IIS and open the site. These are the two sterps that i followed and now it is working fne. |
|
|
|
|