Thursday, August 12, 2010 @ 3:40 pm,WCF,Matt Pavey
"... it appears this is caused by the usage of multiple platforms. It appears that the configuration is only created when consuming the service on my Windows 7 development box, but then not recognized by other platforms such as Windows Server 2003... However due to its staged rollout, it is not fully supported and hence the above errors are generated."
"The fix? Simple for the time being. Just remove the tag and redeploy the configuration."
http://allen-conway-dotnet.blogspot.com/2010/03/dealing-with-unrecognized-element.htmlTuesday, July 27, 2010 @ 10:59 am,IIS,Matt Pavey
Ran into a problem today where I was getting HTTP Error 404.17 after setting up Windows 7 64-bit with IIS7.
"HTTP Error 404.17 - Not Found - The requested content appears to be script and will not be served by the static file handler."
The ISAPI DLL is a 32-bit DLL, so you'll have to either change your default Application Pool to enable 32-bit, or create a separate 32-bit AppPool for your application.
To Enable 32-bit Applications right click on the Application Pool and select "Advanced Settings" then "Enable 32-bit Applications."
Thanks to Scott Hanselman for sharing his solution.
http://www.hanselman.com/blog/HTTPError40417PHPOnIIS7Under64bitVista.aspx
Tuesday, June 8, 2010 @ 5:28 pm,LINQ,Matt Pavey
Dim x As IEnumerable(Of Integer) = From o In Orders From d In o.Details Select d.ProductID Distinct
