Wrox Programmer Forums
|
BOOK: Beginning Visual Basic 2005 ISBN: 978-0-7645-7401-6
This is the forum to discuss the Wrox book Beginning Visual Basic 2005 by Thearon Willis, Bryan Newsome; ISBN: 9780764574016
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning Visual Basic 2005 ISBN: 978-0-7645-7401-6 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old February 4th, 2007, 09:57 AM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default Web Forms

Hi,

I have just started to work through Chapter 17 - Web Forms.

Will the fact that I'm currently running Internet Explorer Version 7 effect the exercises in this chapter? I'm doing the first 'Try it out' in the chapter, and after having added and positioned my 4 controls as directed, what I see in my browser bares no resemblance whatsoever to Figure 17-4. It looks a mess to be quite honest!

Any suggestions?

Many thanks!

Keith

 
Old February 4th, 2007, 03:07 PM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

This problem appears to have cured itself....don't ask me how?? Before, the buttons appeared stretched from one edge of the browser to the other. Weird!

I am however still experiencing issues with this 'Try it out', mainly around differences between what the book says should be happening, and what is actually happening.

Firstly, upon setting up the project, the files in my solution explorer included the web.config file, where as Figure 17-3 does not.

Secondly, when trying to apply code to the OnClick event of the btnClient, it tells me to first set the DefaultClientScript property to VBScript by selecting DOCUMENT from the combo box of the Properties Explorer. I did this, but there was no DefaultClientScript property to be seen. I had to physically change it in the HTML source code.

Finally, my HTML source code did not include a meta object inside the head element.

Any reason for these differences? Am I doing something wrong?

Many thanks!

Keith
 
Old February 6th, 2007, 05:02 PM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I seem to be having immense difficulty with this chapter, and I'd be grateful if someone who's done it could give me some pointers as to what could be going on.

In addition to the issues in my previous posts, I'm now doing Step 7 of the Try It Out on page 568. It tells me to define the master page layout by double clicking on the file in the root directory and update the code where highlighted. If it were a case that all I had to do was update the highlighted code, then I'd be fine, but on my version of the application, I'm having to type out all the code on the following page as well! Is this right?? Shouldn't all this code have been generated automatically, or am I honestly expected to type the whole lot!?

I'd really be grateful for any help.

Many thanks!



 
Old February 9th, 2007, 12:51 PM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Anyone??

 
Old February 11th, 2007, 04:34 PM
Wrox Author
 
Join Date: Mar 2006
Posts: 91
Thanks: 0
Thanked 5 Times in 5 Posts
Default

Hi Keith,

About defaultclientscript.

That has been an issue since the Beta version went to the release. I never figured out if that is a bug or what in Visual Studio. TO work around the issue you can switch to source view on the default.aspx page. That is at the bottom left of the design area. In between the start and end <head> tags put the following

<meta content="text/VBScript" http-equiv="content-script-type" />

Then when you create your client script it will default to vbscript. That is what selecting the defaultclientscript would do for you.

Here is more info from MSDN2

http://msdn2.microsoft.com/en-us/library/5y06x9d7.aspx

Aslo, in Chapter 17 there is another issue on page 576.

You will need to set OldValuesParameterFormatString proterty to "original_{0}" for the asp:SqlDataSource control. Otherwise, you might get an issue about declaring @original_au_id.

Let me knos how you are doing and I will try to help you with your any other issues you are still having.

Bryan



 
Old February 12th, 2007, 01:31 PM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Bryan,

Many thanks for getting back to me!

For the DefaultClientScript property, I ended up doing what you have illustrated anyway. That's not so much of an issue any more.

The main issue now, and what has stopped me in my tracks, is page 568. In my application, I'm having to type out pretty much all the code on both pages, rather than just the highlighted code shown in the book. The impression I get from the book is that all this code should have been there already.

Kind regards,

Keith


 
Old February 14th, 2007, 03:46 AM
Wrox Author
 
Join Date: Mar 2006
Posts: 91
Thanks: 0
Thanked 5 Times in 5 Posts
Default

I think the highlighted code is a little misleading on that page. You will have to either download the code from the wrox site or type it in. You will get better typing it in and it will not be a big issue later as you or coding on your instead of trying to copy from the book.

 
Old February 20th, 2007, 05:09 PM
Authorized User
 
Join Date: Feb 2007
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I'm still having trouble with this. After typing out all the code on page 569, I am getting the following errors:
 
  • First, the DOCTYPE element in my code states the following (note bold text): "-//W3C//DTD XHTML 1.0 Transitional//EN". In the book: "-//W3C//DTD XHTML 1.1//EN".
  • The 'style' element is missing the required attribute 'type' in my application and underlined red.
  • The attribute 'bgcolor' in my application is considered outdated and underlined green.
  • Element 'MenuItem' is an unknown element in my application and underlined red.
  • The 'height' attribute is not a valid attribute of the 'table' element in my application and underlined red.


It is probably so blindingly obvious to a lot of people on here what the issue may be, but I'm a complete novice to Web Forms. I have followed the book to the letter to this point, and it gives no mention or warning that the above errors will/can occur.

It's a shame, since the book has been superb up to this point and I've learnt a hell of a lot, but this chapter has been a total nightmare!

Keith

 
Old February 24th, 2007, 02:49 PM
Wrox Author
 
Join Date: Mar 2006
Posts: 91
Thanks: 0
Thanked 5 Times in 5 Posts
Default

Hi Keith,

Sorry for the delay getting back to you. Can you post your code or email it to me so I can help you. If you click the email poster image in one of my posts you can just email a zipped copy of your project or just the one page zipped up. I cannot receive .aspx ro .vb attachments. Give me a day or two to respond and I should be able to figure this out for you.

Thanks,

Bryan





Similar Threads
Thread Thread Starter Forum Replies Last Post
Web Forms issues bluetonic VB.NET 2002/2003 Basics 0 August 6th, 2006 09:12 AM
how to enbed Word in web forms hawkclj ASP.NET 1.0 and 1.1 Basics 0 July 15th, 2004 03:51 AM
architecture problem with all web forms robert BOOK: ASP.NET Website Programming Problem-Design-Solution 2 August 12th, 2003 02:13 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.