http://blogs.msdn.com/brada/archive/2003/04/16/49975.aspxMore from the dev that owns the loader... If the exception message isn’t enough for you to determine what the problem is, try getting the Fusion log. It will describe the binding failure (if this is due to an assembly binding failure, instead of a loadingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/brada/archive/2003/04/16/49975.aspx#49976Thu, 17 Apr 2003 02:30:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:49976Adam HillCool! Between you and Chris Brume I am learning at least as much as I did from Don Box's book :-) I have a question about the loader though. When moving projects to a test server that *only* involve code behind (no aspx changes) I was using the &quot;rename the surrent dll to xxx.dll_old and put the new dll in&quot; trick, but occasionally I get weird error messages about it not finding the *old* dll. How is the loader figuring this out? If I make a copy of the dll then *copy over* the current dll with the new one. Everything is hunky-dory Am smoking crack or is there a resonable explanation? Keep the geekage! adam...http://blogs.msdn.com/brada/archive/2003/04/16/49975.aspx#9318522Wed, 14 Jan 2009 14:32:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:9318522Fixing the Timer Service when everything breaks down &laquo; Thoughts on computing, SharePoint and all the rest<p>PingBack from <a rel="nofollow" target="_new" href="http://soerennielsen.wordpress.com/2009/01/14/fixing-the-timer-service-when-everything-breaks-down/">http://soerennielsen.wordpress.com/2009/01/14/fixing-the-timer-service-when-everything-breaks-down/</a></p>