Showing posts with label Module Starter Kit. Show all posts
Showing posts with label Module Starter Kit. Show all posts

Debugging a DotNetNuke Compiled Module in VS2008

If you are using VS2008 to create a DNN module with a compiled module starter kit, one option is to attach the project to w3wp.exe process.  You can access it via Debug > Attach to Process... menu.

stolenbit_attach_to_w3wp

If attaching the project to w3wp.exe doesn't seem to be an option somehow (e.g. you just cannot find it), what you need to do now is to modify some project settings as shown below.

In my case, I've create a host record with local.dotnetnuke as the host name.  In your case, you may want to replace http://local.dotnetnuke with http://localhost/dotnetnuke, for example.  Please note that I've saved my project under /DesktopModules/ContactUsForm.  So my project url becomes http://local.dotnetnuke/DesktopModules/ContactUsForm.

stolenbit_debugging_dotnetnuke_compiled_module_vs2008

Save the project and try running it again.  You should now be able to debug the project Wink

DotNetNuke Module Error " It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level."

When creating a DNN C# module using a starter kit on this website, for example, you may encounter the following error when trying to run the module:
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.
Taken a look at the solution created by the starter kit, it creates a web.config file.
This file is what causes the problem.
Just deleting it or renaming it to something else like web.config.bak solves the problem :)
Bookmark and Share