Today also I noticed a new kind of error when I was migrating my existing Silverlight 1.1 control to 2.0. If I add reference of System.Linq.Xml namespace to any existing Silverlight library, I got the below exception when I ran the website.
Now, i have changed the logic so that I dont have to use System.Xml.Linq.
If I find the solution, I shall update it here
Sunday, 20 April 2008
Tuesday, 15 April 2008
Silverlight2.0 Security Tighened??
I am trying to migrate my existing Silverlight 1.1 control to 2.0 version. I noticed another change. Access to other Dlls placed in the folder is denied by System.Reflection. In other words, the Assembly.Load(fullname) does not work unless a reference is added to the assembly.
Though one may say that it is a security feature, it was happening in 1.1. And I dont think loading a silverlight dll from the ClientBin directly will affect the security in anyways.
Though one may say that it is a security feature, it was happening in 1.1. And I dont think loading a silverlight dll from the ClientBin directly will affect the security in anyways.
Labels:
System.Reflection Silverlight2.0
Friday, 11 April 2008
Silverlight System.OutofMemoryException
Today, I encountered a weird exception that I have mentioned in the title when i was building my solution.
I had added many images as assets to a particular project that made it exceed the memory stack. So guys check out.
I had added many images as assets to a particular project that made it exceed the memory stack. So guys check out.
Subscribe to:
Posts (Atom)