If you want to run dasBlog on Windows 2003 64bit IIS6, download the 32bit version and make the following changes.

You will need to replace the 32bit "BasicFrame.WebControls.BasicDatePicker.dll" with the 64bit version available in the source directory "lib".

The file is "BasicFrame.WebControls.BasicDatePicker.dll.64bit", rename it and replace the file"BasicFrame.WebControls.BasicDatePicker.dll" in your "bin" directory.

Restart IIS and problem solved.

Note:

I understand that the compiled version of dasBlog 2.0 is supposed to be CPU agnostic, except for the date picker, which was provided to Microsoft as a freebee created bit specific (a 32bit version and a 64bit version is included in the source, the default setup is for the 32bit .dll).

I understand that dasBlog on Vista IIS7 is a little more involved you may want to read Scott Hanselmans blog on the subject.

http://www.hanselman.com/blog/32bitnessAnd64bitnessAndMigratingDasBlogOnIIS7AndASPNETUnderVista64.aspx

A few words on ISP hosting of dasblog:

 (You should only use the dasblog “web” files for upload installation to a host, keep the directory layout/structure as provide in the zip file)

 ASP.NET 1.1

 Hosts who offer ASP.NET impersonation:

 If your host supports asp.net impersonation there are no permission configuration issues. The only task required of these hosts is to be sure your dasblog install directory is a vdir (Virtual Directory) also know as a (ASP.NET Application directory). If you place your blog in the domain root, this will normally be a vdir by default.

 Non ASP.Net impersonation hosts:

    IIS5 Sites

• ({machinename}\ASPNET): The ASP.NET worker process identity, usually “{machinename}\ASPNET” on IIS5.0 (Windows 2000 and Windows XP) also need read/write access to the content, siteconfig, and logs subdirectories.

     IIS6 Sites

•   (“NETWORK SERVICE”): on IIS 6.0 (Windows Server 2003), also need read/write access to the content, siteconfig, and logs subdirectories.

 Permission gotcha’s: (These can apply to any host situation!)

On some hosts the permissions for files in directories does not inherit properly. To insure that you do not have this problem, you should install dasblog using the following process.

• Create the required directories siteconfig, logs, and content on the host server and insure that they have Read+Write permissions on the remote system BEFORE you upload the dasBlog web files.
•  If there is any concern that permissions were not replicated correctly or you have already uploaded these files and feel you may have a problem, set all the existing files to Read+Wrire permissions.

ASP.NET 2.0

 Hosts running DasBlog on ASP.NET 2.0

 If you are running DasBlog on ASP.NET 2.0, all the preceding applies but you will also need to modify your supplied web.config file to customize your installation for ASP.NET 2.0.

 See the following web.config sections, make the changes documented:

 <!-- ***IMPORTANT*** If you are using ASP.NET 2.0 to host dasBlog

            you must uncomment the httpCookies section below,

            as dasBlog was written for ASP.NET 1.1 and will

            automatically add the HttpOnly flag to cookies automatically -->

 <!---        <httpCookies httpOnlyCookies="false"/> --->

 Note: (The comments tags are the <!--- and the trailing --->)

 <!-- ***IMPORTANT*** If you are using ASP.NET 2.0 to host dasBlog

            you must add cookieless="UseCookies" to the <forms>

            element below! -->

 <forms name=".DASBLOGAUTH" cookieless="UseCookies" protection="All" timeout="60" path="/"/>

 Your entry should look something like the above:

All IIS Sites:

 After you have successfully uploaded all your web files retaining the directory structure that was defined in the download zip file, you the user, or maybe some ISP Hosts who setup dasblog for you will need to accomplish the following:

•  Go to the siteconfig directory in (likely in c:\inetpub\wwwroot\{sitename}) and open the site.Config file. In that file, change the settings (quite obvious when you look at them). The most important change is to set the <Root> value to the proper URL for your weblog.

             Example <Root>http://domain.com/dasblogdirectory</Root>

•  Open the siteSecurity.config file in the same directory and set up your own account with a proper password.

 If all the above have been accomplished correctly, then you should now have a functional dasblog system.