I have tried to set the break point in the on_load event but even that doesn't work

Here's a short list of problems why you might not be seeing the symbols loaded.

BTW the right approach is to load up your project in visual studio (no need to load the entire DNN Core) and attach to the running process.  Some people try and 'run' the entire DNN site - it takes forever to load and generally isn't a good idea.



So onto my list:

1) check that the built version (dll + pdb) was a 'debug' build and your project is in 'debug' configuration

2) check that the .pdb file matches the .dll file in the bin directory

3) check that the .pdb file is in the bin directory

4) check that the asp.net version for the site matches the supported asp.net version of the visual stuido. For example, visual studio 2005 can't attach to an asp.net 4.0 runtime.

5) view the 'output' window in Visual Studio and see if you can pick up on any symbol files that can't be loaded.  For example, you may have built the project in one directory and are trying to debug in another directory.

6) check that you are debugging the right process.  Verify the correct w3wp.exe process is the one running your site. THe output window should scroll through the loaded files if you have the right process, even if your module isn't being correctly loaded to match the debug files.

7) make sure you're running with elevated permissions for Visual Studio (will need admin permission) and also for your worker process.

8) try switching the compilation mode of the web.config file to 'debug' if it isn't already



That's all I can think of at the moment.  Don't give up - there is always a reason and you can always get debugging going if you persist.

Bruce

Your post is Great! Ever i do not have any problems with Debug, but i save it to my Top Links for future. This is the most detailed list about debugging i have ever seen!

Thanks!

Sergey

---