hi guys, have some questions here:
- in chap3, we saw that the reason not using <appSettings> is to avoid the conflict of having same name on two different settings. is that the only reason?
- i found that many settings were hard-coded in configSection.cs. (for example, [ConfigurationProperty("mailSubject", DefaultValue="Mail from TheBeerHouse: {0}")]). why not leave it at web.config? actually, why not leave all the settings at web.config? after all, i thought that's why we need web.config. in this sample site, some settings are at configSection.cs and some at web.config, how do i decide what goes to what?
- at configSection.cs, we have this:
      public string DefaultConnectionStringName
      {
         get { return (string)base["defaultConnectionStringName"]; }
         set { base["connectionStdefaultConnectionStringNameringNa me"] = value; }
      }
i don't know how to come to the setter. what is this: connectionStdefaultConnectionStringNameringName?

hope i can get some answers. thanks!

it'd be greatly appreciated if anyone can help here. i need to understand this part to fully apply this feature. once again, thanks in advance!!

Well for starters, this statement is incorrect:

set { base["connectionStdefaultConnectionStringNameringNa me"] = value; }

it should, expectedly, be:

set { base["defaultConnectionStringName"] = value; }

This was a typo that was filed in the Errata for the book. However, that's about all I can help you with since I have the same questions as to why he has this class, but still uses the web.config for some stuff. More specifically, why is he using base["member"] indexers instead of just using this.member? Or even, base.member? I guess my question should be in a new post...

thanks oooshola for pointing out the typo! finally i got a response.

No prob--I just hope I can help more people and be helped myself, now that I just joined the forum. I'm still in chapter 3! I know I have a looong way to go.