Thanks for the 0.95 "lovin'", Scott. I wish I could say that the upgrade experience was smooth from my existing .094 installation. I had all kinds of fits getting this thing working.
I was running .094 in a single blog configuration operating at the root of http://www.roudybob.net.
Please understand - I am not an ASP or .NET guru. I'm an "infrastructure" geek who knows enough about SQL, ASP and .NET to be dangerous. Most of you who are developer types will look at this post and think I'm stupid and crazy. You're probably right... :-)
I followed the directions as best I could and the result was a mess. I was getting "requested resource cannot be found errors" and "A blog matching the location you requested was not found" errors.
I messed with and messed with (that's probably what got me into so much trouble!) the web.config file. I tried changing the HTTPHandlers configuration as reccomened on the Wiki and changed the "Aggregate" settings for host and URL in the web.config file. I swtiched back and forth between the Single1 sample config and the Single2 sample config and things got worse. At one point, I could get the blog to display, but it thought it was in a multiple blog configuration and I couldn't get to the admin page.
I'm sure the rest of you are much smarter than I, but in case you have issues as well, here are some things I found:
1. Using the Updates .SQL script, I attempted to go line by line as reccomended. I think that's what really got me screwed up to begin with. I must have missed a line or not copied sections of the script intact properly. My reccomendation: Backup, Backup, Backup (yes!) and then run the whole darn script and hope for the best. When I restored from backup and did it this way, the DB upgrade went fine.
2. Start with a clean slate. I removed all the web files from .094 from my site (backed up to my HD) and then copied the new ones clean. Don't try overwriting what you have there. Common sense for most people, I know, but in my haste to get the new bits going, I just dragged and drop to my FTP client.
3. If you have a custom skin installed, change it to one of the in-the-distro scripts like Simple or Blue. I think my HabaHaba1.0 skin was a contributor in fowling things up.
4. If you are getting a "requested resource cannot be found" problem and your web.config file is correct, it might be the Config Table of the .Text ASP.NET Weblogs DB. I don't think the script is working properly (or it didn't in my case). After the Updates .SQL script, I looked at the Config table and found that the BlogGroup column had a value of "1". In a default install of .095, I noticed this was set to "NULL". I went in and modified this to be "NULL", made sure the "Application" column had a value of " ", the "Host" column was set to "roudybob.net" and the errors went away.
5. Make sure the Aggregate values (and the DB provider / Email settings) are correct for your install. For my root-level install of a single blog config, this is what I had:
.Text ASP.NET Weblogs Community" />
.Text ASP.NET Weblogs" />
6. Ignore all the info about the HTTP Handlers. This got me all sorts of confused and I think led to my over analyzing things. I used the Single1_Web.config for my site and it worked fine.
Hope this makes sense. I wanted to get it all down before I forgot!