Jay Hollingum - Works in IT

After publishing the initial default set-up of BlogEngine.NET ( http://www.dotnetblogengine.net/ ) to an IIS 7 web server (i.e. not running under debug mode from Visual Studio), the following security exception may appear, stating : System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. BlogEngine.NET Security Exception To get BlogEngine.NET running, the "User Profile" of the application pool that the application runs under in IIS needs to be updated. IIS 7 Application Pools The "Load User Profile", accessed through advanced settings of the application pool, needs to be set to true.  Application Pool Advanced Settings - Load User Profile That should be it to get a proper response from BlogEngine.NET on the server. Of course don't forget to add write permissions for the app_data folder. Thanks to  David Burke  a

IE8 is a vast improvement on IE6 in terms of rendering HTML and CSS; however now and again there still seem to be some oddities compared to other browsers. Having spent the best part of a day trying to debug the code which had been validated by  http://validator.w3.org/  (as XHTML 1.1 Strict  ) and  http://jigsaw.w3.org/css-validator/  (as CSS 2.1), IE8 was still having trouble rendering the page and was drawing a div twice. Ultimately it boiled down to an anchor tag being closed in short form. i.e. <a id="someAnchor" />. After changing this to <a id="someAnchor"></a>, everything worked fine and was bang on again in IE8. Lesson learnt that if IE8 appears to be rendering incorrectly, check which tags are being closed in which way. Not saying this is the answer to every rendering issue in IE8 but it's something to look out for if HTML and CSS code is perfectly valid, rendering correctly in all other browsers (Chrome, Firefox, Safari, etc.),