Microsoft kill off LINQ to SQL

http://blogs.msdn.com/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx

Microsoft are dropping support for LINQ to SQL as of .NET 4.0. This is a kick in the face for anyone who has invested time in what is a reasonable, if very basic, ORM solution - get porting folks!

I'm just glad I chose to continue using NHibernate.

ASP.NET error: could not load file or assembly App_Web*

Reminder for me more than anything....

Useful information about this annoying error:
http://yetanotherdeveloper.com/post/2008/08/10/Could-not-load-file-or-assembly-App_Web.aspx

Summary of options:

• Turn off batch compilation in web.config (<compilation batch="false"..)
  
• Clear down the contents of Temporary ASP.NET Files (in windows\Microsoft.NET\Framework\vX.xx\)
  

Silverlight and Cross domain services

Silverlight 2 allows you to invoke a web service on a different domain to where your XAP came from. In order to do this however, the owner of the service needs to enable it to allow cross domain calls.

This entails creating an xml file in the root of the service web server called clientaccesspolicy.xml. A skeleton of this file, allowing any caller from any domain, is shown below;

<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
  <cross-domain-access>
    <policy>
      <allow-from http-request-headers="*">
        <domain uri="*" />
      </allow-from>
      <grant-to>
        <resource include-subpaths="true" path="/" />
      </grant-to>
    </policy>
  </cross-domain-access>
</access-policy>