't IsGoud

Back online, altough the server at home functioned quit nicely, it's better to have my blog running at the server of my hosting provider.

For those of you who think everyhting is running smoothly under ASP.NET 2.0 it's a bit of a disapointment. Compiling dasBlog for the .NET 2.0 Framework was not really succesfull.
First build resulted in 52 errors and 75 warnings. I gradually worked my way through all the errormessages and warnings. I stopped at the point were there were no more errormessages and warnings but the application was not running because it couldn't find the culture specific resources.

Just recompiling would have been a quick hack. ASP.NET 2.0 brings so much new possibilities for dasBlog that some aspects have to be rebuild from the ground up. Masterpages for the layout, themes for the skinning, rolebased authoring etc. etc.
After listening to Joe Stagner's podcast with Omar Shahine and Scott Hanselman. I send a mail to Omar to ask him if there were plans to support ASP.NET 2.0. Well there are plans but there is no timeline. So running under 2.0 was not an option I had to get it running under 1.1 again.

My main site is now running under ASP.NET 2.0 while the application directory for dasBlog is running under ASP.NET 1.1. 

Important thing to remember here is that the ASP.NET 1.1 application has to run in it's own application pool. Running 1.1 and 2.0 applications in one application pool doesn't work. So if you need to run multiple websites on an IIS 6 server you have to create separate application pools for the different Framework versions.

I wonder if it works on Windows 2000 and IIS 5? Have to keep that one in mind. Might be an issue at work where we still have a lot of Windows 2000 servers running IIS 5.