Paul Wilson's .NET Blog

I have been using BulkRegister.com for my domains for a few years now.  They added a new feature this last year called auto-renew, so I eagerly setup my domains to auto-renew.  Apparently, this also has the side-effect that no emails are sent at your normal renewal time, since it is supposed to happen automatically.  All the sudden this morning my domain stops resolving while I'm making some minor changes with my web-host's help, and it ends up having nothing to do with my web-host afterall -- BulkRegister just did NOT auto-renew my domain.

Changes in ASP.NET version 1.1 can generate a postback script with a bug in it.  It is particularly a problem for anyone using many of the page template solutions.  I posted both C# and VB workarounds on the ASP.NET forums, and here's the C# code:

In reference to my last entry on "AppSettings can Reference an External Config File", John Mandia asks:

I recently discovered that the app/web.config file can reference an external config file to get some or all of its appsettings.  You don't have to name it with the extension config, but that's best since its protected from anyone browsing to it, and since it has the support of the VS.NET editor.  You can have keys that are only defined in the external file, or you can override keys that were already defined in the app/web.config file.  One great use of this would be to store your database connection string, or other settings that may vary from development to testing to production.  I did notice that changes made to the external config file are not automatically picked up until the app restarts, but thats easy to force by simply editing the real app/web.config.  By the way, this does fully work in the original version 1.0 .NET framework, although it was apparently undocumented until 1.1.  Sorry if someone else wrote about this -- I can't remember where I first saw this tidbit recently -- I think it may have been in the last MSDN Magazine but I'm not sure.