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.0Custom Module Debugging DNN 4.9 & VS2008Custom Module Debugging DNN 4.9 & VS2008
Previous
 
Next
New Post
1/6/2009 4:57 AM
 

Hi All,

So i have the following setup,

  • DNN Installation 4.9 (Install Version)
  • Custom Module (WAP) using .net 2.0
  • Using VS 2008

My only problem is debugging, i can debug using the 'Attach to Process'. Is there a way that i can debug without the 'Attach to Process' method.

I read the blog that cnurse posted here but i don't have the settings that cnurse had in his screenshot. I am using XP professional 32 bit and IIS 5.1

Any comments would be really appreciated :)

 

Thanks a lot

 

Ruben

 

 

 
New Post
1/6/2009 10:10 AM
 

So, in the settings for your project (a WAP in VS 2008, right?), what do you see on the Web tab?  As I understand, the main thing you need to setup to enable F5 debugging is to make sure that the startup URL is set to the right website.  Otherwise it should automatically connect to the aspnet_wp process.

However, we've found here that attaching to the process is quicker and simpler than using the F5 method, but certainly results may vary .

Hope that helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/6/2009 8:08 PM
 

Hi Ruben - I only ever use 'F5' debugging and I make sure the Web.config contains compilation debug="true" strict="false">

It seems to me you can ignore the IIS Properties / Virtual Directory > Configuration / Debugging  debugging flag settings, they don't make any difference to this issue.

If you then want Client-side debugging then you really need the Script Explorer window. However, I have found, only in DNN, that this is pretty useless because there are nearly too many other DNN errors getting in the way before it reaches the point you want to Debug. Perhaps somebody could clarify why this should be so?

 

 

<

 
New Post
1/13/2009 5:03 AM
 

Thanks all for the replies, well first of all when i converted the solution i had a problem since i converted from vs 2003 - vs 2008 the project was not convert to WAP. This was solved as i said in this post.

After I got my project convert to WAP i had the same options as the blog post by cnurse. Once i did the changes that are listed in the blog post, everything worked like a charm .... yey....

brian, while i do agree with you that attaching to the process is quicker and simpler, i found that (could be i had not enough coffee ) if a developer doesn't pay attention to which process he is attaching his project, he may end up debugging a previous version of the project. Happened to me i didnt refresh the page and .... well you can guess the rest :) hehe ... i know rookie mistake probably :)

Thanks a lot for your replies,

 

Ruben

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Module Debugging DNN 4.9 & VS2008Custom Module Debugging DNN 4.9 & VS2008


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