Say for instance you have an online store, offering a new product to a segment of customers. The path to the catalog item is
- http://AcmeCorp.com/store/catalog.aspx?productid=TY3466a&customerid=143044&branch=south
- http://AcmeCorp.com/store/MultiVitamins.aspx
The highlighted section specifies the url mapping. The vanity url's (Diablo_Config.aspx and Diablo_Config.aspx?loc=test) are actually just as complicated as the actual paths (testconfig.aspx and test/testconfig.aspx), but it illustrates what's possible. The following screenshots illustrate what the "customer" sees:
The aspx page that outputs the appSettings is simply copied to the application root and /Test folder for illustrative purposes. If you're interested in aspx (not code-behind) that references app settings, see the following link.
What namespace is required to use the ConfigurationManager ?
ReplyDeleteThe System.Configuration namespace. In VS.NET 2005, you have to add the System.Configuration.dll as a reference.
ReplyDeleteHow about I don't add a reference but only mention at the top of my .cs file as
ReplyDeleteusing System.Configuration
Will it work ?
Thanks,
In my version of VS.NET 2005, it will not work :).
ReplyDeleteIt cannot have effect in actual fact, that is exactly what I think.
ReplyDeleteGreat site!!! this information really helped me
ReplyDelete