Wrox Programmer Forums
|
BOOK: Professional DotNetNuke Module Programming ISBN: 978-0-470-17116-5
This is the forum to discuss the Wrox book Professional DotNetNuke Module Programming by Mitchel Sellers and Shaun Walker - Wrox DotNetNuke Series Editor; ISBN: 978-0-470-17116-5
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional DotNetNuke Module Programming ISBN: 978-0-470-17116-5 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old March 20th, 2009, 01:53 PM
Registered User
 
Join Date: May 2004
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Module Debugging

I have built the Guestbook Module in VB and installed it in an instance of DNN 5.0.1 running on a local machine. The module throws an error and I would like to debug but the instructions in Chapter 9 to attach the Module to the Visual Studio Debugger are unclear.

Has anyone successfully debugged their Guestbook Module using Visual Studio 2008? If so, how did you do it?

Thanks for the help!
 
Old March 31st, 2009, 12:52 AM
Wrox Author
 
Join Date: Jul 2008
Posts: 74
Thanks: 1
Thanked 8 Times in 8 Posts
Send a message via MSN to msellers
Default

Ross,

With the IIS installed version of DotNetNuke running you can within VS select "Debug" -> "Attach to Process". The window that will appear will show you all running processes on your machine.

You will want to select the process for ASP.NET. If on Windows XP it will be aspnet_wp.exe (or similar). If on Vista it will be w3wp.exe

Now, you will want to set a breakpoint to be able to step through the code, just prior to the error. The reason for this is that if you are allowing DNN to log the error, it isn't unhandled, and will not cause an automatic break with the debugger.

Once you have setup the breakpoint simply go to the module and perform the action that was causing the error, the debugger should take you into your code to start stepping through the code.
__________________
Mitchel Sellers
Microsoft C# MVP, MCITP
Director of Development
IowaComputerGurus Inc.

My blog for .NET and DotNetNuke info

Author of "Professional DotNetNuke Module Programming"

Tech Editor on "Visual Studio 2010 six-in-one" and "Pro C# 4.0"





Similar Threads
Thread Thread Starter Forum Replies Last Post
module umeshtheone Beginning VB 6 2 May 17th, 2007 05:48 AM
module umeshtheone VB Databases Basics 1 May 14th, 2007 01:41 PM
new module FT BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 2 March 15th, 2007 06:06 AM
module? flora8 Access VBA 2 September 7th, 2006 11:10 AM
Module sohrabus ASP.NET 2.0 Professional 1 September 1st, 2006 12:26 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.