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

HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...module debuggingmodule debugging
Previous
 
Next
New Post
11/29/2011 1:19 PM
 
Hi there,
I need to know how to setup VS2010/2008 to debug a module with IIS . .
I have a windows server 2008 standard , IIS 7.0.6000 ,sqlserver 2008 and DotNetNuke_Community_06.01.01_Install dotnetnuke version
I followed this tutorials :
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/VideoId/15/Basic-DotNetNuke-Module-Development.aspx
and everything  worked fine until I tried to debug my module .
 After I set up the project url (to make VS and IIS work together) VS creates
another virtual directory  for the folder where is my project module . In tutorial is nothing mentioned about that .
Well  I create this virtual directory , but when I try to run the module in debug mode it prompts me
to create a web.config(my module does not have a web.config file) with the we option debug=true otherwise will run in normal mode .
If a choose to create the web.confg file the module installed on a page in dotnetnuke site will not work anymore  . I run into this exception
"DotNetNuke.Services.Exceptions.ModuleLoadException: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS."
That's because I have another config file , one upper level , of the dotnetnuke instalation . It's
kind of vicious circle .
Thank you !
 
New Post
11/30/2011 4:13 AM
 
you need to include DNN web site in your solution and specify the web site to be the start project. make sure, no virtual directory is created for your module (which needs to reside inside /desktopmodules folder or a subfolder of it). set debug to true in web.config and make sure, you compiled your module for debug.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...module debuggingmodule debugging


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