Hello again.

Today a really small post from me about a really simple thing i found out today. Ofcourse a lot of people know this but i also know lots of people dont know this while you are using it quite often. When you are developing for SharePoint for example you'll have to debug by attaching your debugger to the right w3wp.exe process. When i did this i always selected 1 and hoped it was the right one. Today i was debugging together with a collegue and then he selected more processes at once and i was like *DOH*!!!

This discovery can save a lot of time if you always pick the wrong w3wp.exe process like i did :)

so for everyone who didnt know this use this option from now on. I will do it for sure!

Geert van der Cruijsen

Today Microsoft promised Internet Explorer 8 will use the 'super standard mode'  rendering mode by standard instead of the IE7 version 'Quirks mode' that was planned earier.

Because of this People will be forced using the W3C standards OR add a special tag so the browser knows it should render the page in IE7 mode. Hopefully this will help to have 1 standard html which every browser will show the same way. More information about this: http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx 

With this change IE8 will be able to pass the ACID2 test but guess what the "Web Standards Project" released the ACID3 test today which is supposed to test Ajax and other dynamic content in browsers. IE7 get's a score of 5 out of 100 while FireFox is getting the current best score with 50/100. Still a long way to go for every browser to pass this test. You can find the test and more information here: http://www.webstandards.org/action/acid3/

Geert van der Cruijsen

The photo sharing site Flickr has a nice api which you can use in your own applications. On codeplex is a .net version of this api Flickr.net.

I had to make a little script for a friends project so she could view random flickr photo's on her site. I made a aspx page using the Flickr.Net dll and it worked perfectly on my own machine. after uploading it to my hosted webserver i ran into trouble. the following error came up when browsing to the aspx page

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

After some research i came to the conclusion that it had something to do with my site running in a medium trust. The Flickr.Net api uses a caching function standard which doesnt has the right permission on a hosted envoirment.

The real solution was easy after i found out what the real problem was. The only thing i had to do was disable the caching:

After doing this the script was running perfectly. during the search for the solution to this problem i came across a lot of people who had the same problem when deploying their Flickr.net enabled scripts so i thought it was handy to post this simple solution.

Have fun with your Flickr.Net enabled Scripts!

Geert van der Cruijsen