Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.0Debugging the coreDebugging the core
Previous
 
Next
New Post
12/17/2006 10:22 AM
 
Jon

Joined: 10/25/2006
Posts: 84
I want to set breakpoints on code that is compiled into DotNetNuke.dll, but I haven't the first clue how.  I'm a Win32 developer.  I've never done any ASP.NET development.

My DNN development machine is Win2000 Pro, with IIS installed, MS SQL 2000, Visual Web Developer 2005, and DNN 4.3.5.

The code I want to debug is DotNetNuke.Services.Localization.PersonalizeSystemMessage.  I know this is in Library\Components\Localization\Localization.vb.

I can open my DNN website in VWD.  I can rebuild the website.  I installed the DNN site using the source package.  But nothing in the Library folder shows up in my project.  I don't know how to set a breakpoint in Localization.vb.

Any pointers, including references to tutorials, blogs, posts, etc, would be helpful.  I've read through Michael's tutorials.  But these center around creating new things versus working in the core.

Thanks
 
New Post
12/17/2006 7:11 PM
 
Philip Beadle


Joined: 1/7/2003
Posts: 1822

Hi Jon,

What you need is the DotNetNuke_4.3.7_Source.zip.  Unzip it and set up the virtual directory database etc.   You will need Visual Studio 2005 to debug the component library.  VWD is not capable of debugging projects.

Cheers

Philip Beadle - Employee
 
New Post
12/18/2006 12:30 AM
 
Jon

Joined: 10/25/2006
Posts: 84
Thanks Michael.  The Source.zip has two folders, website and library.  I have these folders extracted to my C:\inetpub\wwwroot folder.  I assume that my IIS configuration should point to the c:\inetpub\wwwroot\website folder, which it currently does.

I have access to VS2005, but have not installed it yet.  I'll try to do that tomorrow.

But once I have VS2005 running, what then?  Will I open DotNetNuke.Library.vbproj in VS2005?  How will my DNN install know to use the version I'm running in VS2005 instead of the DLLs in the website\bin folder?

Obviously, there are still steps that I don't understand.
 
New Post
12/18/2006 12:41 AM
 
Philip Beadle


Joined: 1/7/2003
Posts: 1822

You'll see there is a DotNetNuke.sln file in the source zip as well.  What you do is set up your Virtaul directory then update the lines

Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "http://localhost/YourVirDir/", "http://localhost/YourVirDir", "{79D3BA0F-F76F-4A84-AE7F-C6A01EC247F9}"

When you open it it will have http://localhost/DotNetNuke_2 in there.  Just switch it to your virtual directory which doesnt have to be in C:\inetpub\wwwroot it can be anywhere.  You just set the source folder when you set up the Virtual Directory.

Then open VS2005 and open the sln file from the Open Project menu item.  This will open the solution with all 50+ projects in it. 

Have fun.

Philip Beadle - Employee
 
 Page 1 of 1
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Debugging the coreDebugging the core


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