Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN 4.01 + VS2005 - Debugger not workingDNN 4.01 + VS2005 - Debugger not working
Previous
 
Next
New Post
2/1/2006 9:27 AM
 
It depends on whether you are using a source install or the starter kit. For the starter kit, when you first setup the project, there is a dialog box that lets you pick "File System/HTTP/FTP". File system is the built in server, HTTP is IIS. You need adminstrator's rights on a system to debug IIS.

For the source code, it is already setup to use IIS. It does require some setting up though. I won't go into details here as there are several posts on the ASP.Net forums that go into it in detail. In fact there is a pinned post there that may be useful. Also check the forums here as I remember seeing a post on creating custom modules.

Before you can debug in either though, the DNN must be built successfully and you should be able to browse the default site.

Finally, it would be useful if you could please post the details of any errors, or specifically what is going wrong. You should not need any specific "settings" to get debugging to work. There are some pitfalls however that others can help you with if you provide details on what is going wrong.
 
New Post
2/1/2006 1:12 PM
 

I installed the DNN source and got it up and running.  That's not the problem.

More accurately, I then installed the C# and VB "template" files that merge with VS2005.  Those are the ones that build default custom modules.  I think that came from from the starter kit install, which was a .vsi file.

To be perfectly clear, my problem is not getting DNN to run.  It runs fine on my machine.

My problem is not to get the default custom C# modules I create using the templates added to VS2005.  I can do that.

My problem is not in getting the debugger to work with VS2005, when I write a non-DNN ASP.Net application.  I can do that.  It "just works".

My problem is that I cannot get the debugger to work with DNN 4.02.  I set the breakpoints, and run the debugger, and it's as if I wasn't using the debugger at all.

Why do I want to use the debugger if DNN is working fine?

Well, I want to customize those default modules I created with the template, and using the debugger makes it easier to find my mistakes.  It also makes it easier to understand exactly what is happening in the DNN code.  DNN is a great learning resource and I'm trying to make the most of it. 

"For the source code, it is already setup to use IIS. It does require some setting up though. I won't go into details here as there are several posts on the ASP.Net forums that go into it in detail. In fact there is a pinned post there that may be useful. Also check the forums here as I remember seeing a post on creating custom modules."

I'll look there.  Thanks!

"Finally, it would be useful if you could please post the details of any errors, or specifically what is going wrong. "

No it wouldn't.  :)

There's nothing wrong with DNN, no errors for someone to fix.  I just want to use the debugger for the reasons given above. :)

 

 
New Post
2/1/2006 3:17 PM
 
Ok David, now I see the problem. In all of your previous posts, you never specified that breakpoints were not being hit. :)

At any rate, have you "added" modules to a source install, or to a starter kit site?

Try setting a breakpoint in Default.aspx.vb in the Page_Init event to see if it get's hit or not. That way you can tell if breakpoints work or not since that is always hit on every page load.

Good Luck
 
New Post
2/1/2006 3:52 PM
 

Sorry for not being clear enough! :)

Yes, I've added a new custom module using the starter kit.

But breakpoints simply do not work at all for the DNN code.  I've put them in Default.aspx.vb and I've put them in my own .cs files.  Nothing happens.  If I write text messages to the page via HttpResponse, I see them, so the code is being executed.  But the code execution doesn't stop at the break points.  I'm puzzled, to say the least.

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN 4.01 + VS2005 - Debugger not workingDNN 4.01 + VS2005 - Debugger not working


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out