404's and Master Pages
Three weeks since my last post, and I've had something interesting to talk about almost every day. The last few days have been a blur of typing as I implement the coolest thing since sliced bread.
But I can't tell you about it, so you'll have to put up with my silence until it goes to Beta at least. I know that sucks, but you've got the better end of this deal - in five minutes you'll be somewhere else and I'll still be sitting here wanting to show you this stuff.
But this post is really about a weird issue I just came across when I was hacking away at my Master Pages. The app I'm working on is like a pack of toothpicks being thrown into the air literally every hour and being re-assembled, so it gets hard sometimes to put cause and effect together.
And in this case it was weird enough to blog about.
The issue was that I started getting 404's thrown for an aspx page.
The aspx page exists on disk. It has the normal persmissions (I was already grasping at straws). The solution builds perfectly, but when I try to view that page I get a 404.
The cause turns out to be the Master Page. I had deleted a user control that it referenced, and that put it into some kind of tailspin that resulted in the 404. Looking at the Master Page n the VS designer showed the red squigglies that pointed out the real problem.
One more out there in GoogleSpace.