If you are trying to make a web request from a Silverlight application the first thing the Silverlight runtime will do is request a security policy file (see Network Security Access Restrictions in Silverlight) from the root of the server you are making your web request to. This happens if you are making your request using the HttpWebRequest or WebClient class. If the Silverlight runtime fails to get a security policy file your web request will fail. If your Silverlight application relies on this web request then you are going to need to contact the server owner and get them to add a security file but until then you can use the Fiddler HTTP Proxy to trick the Silverlight runtime into believing that it does have permission to make the request.
(More …)
Latest Updates: Microsoft RSS
-
Using Fiddler to trick Silverlight into allowing a crossdomain Web Request
Phil Leggetter
-
Microsoft Bing.com round table thoughts
Phil Leggetter
A couple of days ago I blogged that I was going to attend a Microsoft bing round table. I’ve now attended and here are the key points and interesting facts that I took from the event. You can also search for #meetbing on twitter for relevant tweets.
(More …) -
Bing.com round table
Phil Leggetter
On Monday between 19:00 and 21:00 I’m going to a Bing roundtable (round table) in London. The event is being organise by Colin Mercer and is described as:
a small round-table event to discuss Bing and since we saw your recent tweet regarding comparative search results between Bing and Google, we thought that you might be interested in coming along. The idea would be to get your initial thoughts and you’ll get an update on the future steps for Bing which are being developed specifically for the UK. During the session you’ll have the chance to talk with Microsoft representatives and other people from social media like yourself, who have expressed some early opinion.
-
Live Mesh - my experience
Phil Leggetter
I think that Live Mesh will be really useful. I think it provides great benefit to individual users, such as myself, and has great potential to be used by software solution developers. I’m presently using it to synchronise some files that I want to backup and be available wherever I am.
I originally had a lot of web files being synchronised, around 700MB, but the synchronisation was taking ages and killing my CPU. CPU was sitting at 100% and there was no sign of things completing. I think it was having a problem with the volume of small files.
To summarise: it’s a great product with bags of potential but something needs to be done to reduce the CPU usage when dealing with the synchronisation of a large volume of small files.
