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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke package with Debugging SymbolsDotNetNuke package with Debugging Symbols
Previous
 
Next
New Post
6/17/2008 10:21 AM
 

Brandon's random idea of the day:

Has anyone on the core team considered releasing debug version of the DNN assemblies (with symbols) as a separate download?  Time and time again I am faced with a situation where someone is having a problem and all I have to work with is a call stack.  Sometimes the stack is enough to narrow down the problem, but often I am forced to guess about the point of failure.  I'm sure many others have been in this situation as well.

If I could advise people having a serious problem to temporarily install the debug-enabled assemblies and reproduce the error, I'd have line numbers to work with.  For many problems, this would greatly speed my efforts -- and in some circumstances allow me to isolate a problem I would not other wise locate.

Any thoughts?

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
6/17/2008 11:54 AM
 

Brandon,

With the source version of DNN you can build it in Debug mode yourself if you need the debug enabled assemblies.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
6/17/2008 12:16 PM
 

Hi Mitch,

I think you may have missed the thesis of my post.

While I'm aware that I can do that (and already do), my post was really related to helping others who are experiencing problems and ask for help on the forums.  Many (most?) users who post seeking help aren't able to debug the problem themselves, and asking them to recompile the core with symbols seems a bit beyond their abilities.  Often, just retrieving a call stack is a challenge for the audience to which I refer.

However, downloading a debug package and copying it into a bin directory seems like something that most could accomplish, and might yield a solution to some of the more arcane problems more readily.

Just an idea.

Brandon


Brandon Haynes
BrandonHaynes.org
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke package with Debugging SymbolsDotNetNuke package with Debugging Symbols


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