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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The breakpoint in DotNetNuke can not be hit The breakpoint in DotNetNuke can not be hit
Previous
 
Next
New Post
9/22/2008 4:16 AM
 
zhaodengpan

Joined: 6/17/2008
Posts: 12

I am mad. Can anybody help me?

I use the following step to get the problem.

1. I use DotNetNuke 4.9.0 install edition and installed a new site.

2. The website work ok.

3. I set a break point in Default.aspx.vb's Page_Load Method and start to debug. A hollow circle with a warning symbol appears to the left of the breakpoint an when the mouse pointer is placed on top of this it shows a message. "The breakpoint will not currently be hit. The source code is different from the original version".  How can I get rid of this hint? The breakpoint on other code line can not be hit similarly.

4. Other VB website is ok in my dev environment.

5. I debug the 4.8.4 version and get the same result.

I use visual studio 2005 team suit editon.

Can anybody help me? Other people get the similar problem and can not get a solution. See: http://www.dnncreative.com/Forum/tabid/88/forumid/4/postid/8585/view/topic/Default.aspx

 
 
New Post
9/22/2008 8:45 AM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

erikvanballegoij.com
Joined: 4/7/2004
Posts: 4445

do you have debug enabled in the web.config? if you used release.config, its disabled by default

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
9/22/2008 9:45 PM
 
zhaodengpan

Joined: 6/17/2008
Posts: 12

My web.config about compilation is as follow.

 <system.web>

              <compilation debug="true" strict="false">
 

If I change the strict to true, many compilation errors exist.
 
New Post
9/22/2008 10:03 PM
 
Nicholas Lu

Joined: 5/1/2005
Posts: 184
  1. Do you modified the debug section in web.config to debug=true?
  2. You can try to use Attach to Process
  3. You can try to rebuild the DNN solution at first to solve the ource code is different from the original version problem.


Microsoft MVP
Professional DNN Module Developer
 
New Post
9/23/2008 4:43 AM
 
zhaodengpan

Joined: 6/17/2008
Posts: 12

Nicholas Lu wrote
 

  1. Do you modified the debug section in web.config to debug=true?
  2. You can try to use Attach to Process
  3. You can try to rebuild the DNN solution at first to solve the ource code is different from the original version problem.

Nicholas Lu wrote
 

  1. Do you modified the debug section in web.config to debug=true?
  2. You can try to use Attach to Process
  3. You can try to rebuild the DNN solution at first to solve the ource code is different from the original version problem.

The all methods you mentioned are not work.

The breakpoint will be hit only when I uncheck the "Require source files to exactly match the original version" general debugging option on VS's Options dialog which can be open by click VS's Tools---->Options menu. 
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The breakpoint in DotNetNuke can not be hit The breakpoint in DotNetNuke can not be hit


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