Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0
This is the forum to discuss the Wrox book ASP.NET 2.0 Website Programming: Problem - Design - Solution by Marco Bellinaso; ISBN: 9780764584640
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #11 (permalink)  
Old May 16th, 2008, 02:57 AM
Friend of Wrox
Join Date: Mar 2007
Location: Creetown, UK
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts

quote:Originally posted by LAM
quote:Originally posted by Lee Dumond
 Your UpdateProduct method seems to have uniCost instead of unitCost as a parameter. Could that be it?
Apparently the problem is solved. You were right!!! I had uniCost (no "t" in unit) as a parameter in the UpdateProduct method. I was looking at other overload of the same method that had the correct unitCost parameter.

Anyway, shouldn't .net care about the type of the parameter (string, int, etc) and the position (method signature) instead of the actual name of the parameter??

Thanks so much for your help!!! I really appreciate it.

Take care.

LAM - the name of the parameter (as well as obviously the type) coming from the aspx page is important as .net uses reflection to match this up at IL level. But you've learned thro' an unfortunate circumstance (i.e. an actual published typo) that this is the case. equipped with that knowledge, it's probably unlikely that that particular nuance or error will occur again in your quest :D. another great example of this is action is the 'invisible' paging parameters which have default names of startRowIndex and maximumRows. you'll notice that if you give your BLL class method different parameter names for these values (i.e. startRow, maxRow) that a similar error will be thrown by the compiled code. trying to track that down can be a nightmare unless you know about this quirk.

i'd recommend also that you download the codeplex version of the code just so you know how the final rendition looks/feels.




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
New.aspx works but login.aspx fails Validation nigelhamilton BOOK: ASP.NET Website Programming Problem-Design-Solution 8 September 13th, 2004 02:29 AM
New.aspx works but not Login.aspx ? reidcor BOOK: ASP.NET Website Programming Problem-Design-Solution 2 May 24th, 2004 10:32 AM
new to ASPX wesamo ASP.NET 1.0 and 1.1 Basics 2 April 19th, 2004 11:50 PM
HowTo Pass Form data from Page1.aspx to Page2.aspx dati ASP.NET 1.0 and 1.1 Basics 6 January 27th, 2004 06:57 AM

All times are GMT -4. The time now is 06:56 PM.

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