I just realized I made a mistake. You can't compile the .aspx page directly. Instead, you have to locate the temporary .vb file, and you can compile that one. ASP.NET creates that temp VB file by manipulating your .aspx page.
I'd start by rebooting. Then, don't use ThePhileVB after the boot. Instead, locate the temp path for this application and delete the files there. Mine was located here:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Tempo rary ASP.NET Files\thephilevb
Now, bring up a browser, but don't go into ThePhileVB yet. Just go directly to the page giving you trouble. Leave your browser up, then go to that temporary path mentioned above (it got recreated just now), and find the .vb file for that page (it will have a wierd name, but it will end in .vb). You should be able to compile this .vb file from a batch file. Make sure you run the batch file in a VS Command prompt - this gives you the right path.

Eric

Thanks again, Eric...now I have some work to do....

but can you tell me one thing...look at the error message above
in my original post. Even with web.config set to mode="off"
(or "RemoteOnly") for customErrors, this type of error information
is all I get, no matter what page has an error and no matter
what the error is. Shouldn't I be getting the detailed error with
the lines of code, and the hyperlinks for "detailed compiler
output" ? I don't ever get these like I used to in WebMatrix
with in-line coding.
Thx,

R Corcoran, Jr.

It seems like you should get detailed errors, but he's handling exceptions in many places. He is not passing you all of the information when exceptions are raised. global.asax.vb is an easy place to look, but there are other places where this is being done. That's why I suggested comiling the page yourself. That's what I would do. You don't want to disable the exception handling because it's pretty good in general. Once you've got the site working you'll definitely want to keep the exception handling.

Eric

Reidcor,

Let us know if you are successful in getting this to work.

Thanks for your help Englere!

XUMUSKIEFAN
Wrox Moderator

I have the same problem, bat I don't understand this discussion because i'm italian. Can you explain our solution to this error???
Thanks

I have the same problem, in the Forums on Topic.aspx
I stripped the code and put it back piece by piece,
and got the error when I inserted this LinkButton (Line 74):

                                    <asp:LinkButton id="DeleteTopic" Runat="server" OnClick="DeleteTopic_Click">
                                        [
                                        <img src="./Images/Delete.gif" Alt="Delete this topic" border="0">
                                        Delete ]
                                    </asp:LinkButton>

When I left out the "OnClick" aspx event, there was no error.
Anyone Ideas?

Some things I have found out:

Exception occurs when saving in design view. Then it replaces all '&' characters with html entities '&amp;'. Seems to be an IDE bug.

Also this exception can get thrown if there are errors in the codebehind, e.g. when you are calling a function that generates an error, or you have a typo and the function doesn't exist in the code behind.

Instead of OnClick for the Linkbutton I used CommandName="delete" now it works.