BasePage Question

Rushino · April 8th, 2010, 04:47 PM

Hello,

I am at the page 212.. and you tell us to replace all the System.Web.UI.Page with BasePage. It is all the files including thoses in Demos folder ?

Thanks.

Imar · April 8th, 2010, 05:01 PM

Yes, if you want to, you can. By using Find and Replace, you replace all instances of System.Web.UI.Page, and thus the ones in the Demos folder as well. To be able to run them, you need to give them a valid title.

Before you edited your post, you said you had compile time errors. Is that still the case? If so, can you post the markup and code behind of one of the pages that generates an error? (Please use the code formatting toolbar on the editor when posting).

Hope you're enjoying the book.

Cheers,

Imar

Rushino · April 8th, 2010, 05:12 PM

Well, at first i wanted to ask the question ive asked now.. but after executing the files in the Demos folder using the "Start Debugging" (Green Arrow of IDE) i found that the error is raised from the IDE, an exception was raised there about the title and not in the browser so i wondered why cause doing the same for the login.aspx or default.aspx result in the executing inside the browser..

So when i use the "Debugging" I though that the small green arrow was the same as CTRL+F5 but look like i was wrong. The green arrow execute code inside the IDE which CTRL+F5 run the code in the browser by launching it. However, using that green arrow for the login.aspx and default.aspx work perfectly.. but using it for the files inside the Demos folder... cause problems or errors.. i still wonder why ?

Anyway the Green arrow is confusing.. cause it look like it mean "Run"..

Imar · April 8th, 2010, 05:26 PM

F5 (green arrow) means: Compile, and run with the debugger enabled
Ctrl+F means: Compile, and run without the debugger enabled

Both should compile the applicaton (if it's an ASPX page you're requesting)

Chapter 18 digs deeper into compilation and debugging.

What errors are you getting?

Imar

Rushino · April 8th, 2010, 05:30 PM

So with the debugger enabled its gonna keep trace of error inside the IDE and without it enabled it gonna execute in the browser. I am right ?

Well the error i was getting are the exception we created. No worry.

Imar · April 8th, 2010, 05:41 PM

Quote:

So with the debugger enabled its gonna keep trace of error inside the IDE and without it enabled it gonna execute in the browser. I am right ?

Both options do a compilation, and thus any compile time errors (syntax errors and so on) are shown in Visual Studio before you're even able to run the page in the browser. However the behavior for the BasePage should indeed result in a runtime, and not a compile time error.

What you may be seeing is that Visual Studio breaks into your code when you debug (by using F5), showing you the line that throws the error. This is normal behavior (and very useful when tracking down bugs). When you then press F5 again, you should see the error message appear in the browser. When using Ctrl+F5, you will see the error in the browser directly. It's still being caused by a run-time error at the server (e.g. the browser just displays the error message), but Visual Studio doesn't intercept it, and doesn't show you where the error occurred.

Does this help?

mar

Rushino · April 8th, 2010, 05:47 PM

Yes. Thanks.

Aslo.. i am impressed so far about how ASP.NET 4 is useful and easier than PHP in many ways.

Imar · April 8th, 2010, 06:03 PM

That's good to hear. And how do you like the book?

Rushino · April 8th, 2010, 06:19 PM

I love it ! I just can't wait to get through it ! It is very pleasant to read and it is probably one of the best books ive read so far. Be sure that i will review it on amazon as soon as i finish it and so far it deserve 5 stars. Its sad that the cover got a bit damaged through the transport but well doesnt matter its minor.

Imar · April 9th, 2010, 12:48 PM

Excellent!. Looking forward to your review.

Cheers,

Imar