I had the same problem. You have to right click on your solution in the solution explorer and click properties. Than on the left select configuration properties and click configuration manager on top right. Under the configuration colum change your project from "RELEASE" to "DEBUG". This worked for me so I hope it works for you.

GORAN

>> If I change the names of the two aspxs I can set breakpoints successfully. If I change them back, the problem reappears. If I remove the files from my project, and then add two new files with the same names, and paste in the original content, the problem persists.

I'm experiencing this exact symptom. I've deleted every related dll and pbx on the server and rebuilt - No joy. I can set a breakpoint on other pages in the solution.

Crazy.

I think you can't debug into a source file named the same as another source file in the same project or solution. I didn't check on this myself, but that's what seems to be happening. Why don't you just make each page have a unique name?

The biggest problem often comes from having multiple pages named Default.aspx. This isn't a good idea, but it seems like it would work if they're each in a separate folder.

The problem is not a .net runtime issue - it only affects debugging with Visual Studio.

Eric

pls. see this link for resolution:

http://www.wilsondotnet.com/Tips/Vie....aspx?Thread=6

dolanz

Solution

Check your aspx or ascx page control Debug property. Set Debug="True"

<%@ Control Inherits="MyTestPage" debug="True"
language="vb" AutoEventWireup="false" Explicit="True" enableViewState="True" CodeFile="SiteSettings.ascx.vb" %>

It will work........