Silverlight Emotional Handbook

code, silverlight — Szili @ 8:20 pm

I met her. I fell in love with her. Now I need a frickin’ handbook for her emotional life…

Silverlight Error Codes Explained!
Comprehensive error collection with solutions!

“Requested registry access is not allowed.”
When trying to create a new C# Silverlight project in Visual Studio 2008 Beta 2 under Windows Vista.

  • Turning UAC back on didn’t work.
  • Vista re-install did work (if you call this a solution..).

It happened again after installing Visual Studio 2008. When trying to create a new c# poject I got the error message saying “Requested registry access is not allowed.” But this time i did found a solution:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2400179&SiteID=1
The only trick is to rename the vb* to cs* files in the cmd file.

Point class hell.
Point class problems caused by regional settings. Dot vs. comma stuff.

Silverlight Loaded Event and Object Initializers

Frameworkelement and System.ArgumentException

Xaml stream is null

Children.Add Freeze

If the app freezes on Children.Add check the objects Load events in the code and Load triggers in its Xaml.

System.Exception after Storyboard.Begin()

You haven’t added the Storyboard to a Children collection.
The Storyboard is not a descendant of the Page.

Control Width and Height

Control inherits Height and Width from FrameworkElement, but is not aware of the Control implementation root concept.

An important line I believe. It resolves a great amount of confusion in me. Source

Silverlight control over silverlight control

Every control should have isWindowless:"true" property set in its createSilverlight() function in the javascript files.
The ones with transparent background should have their background property set to transparent: background: '#00000000'
Then you can set their order in css with z-index.

Setting properties of objects created from xaml.

You can not set the value of a property which wasn’t declared  in markup.
For example, setting the Storyboard.Target of a DoubleAnimation in codebehind will throw a CatastrophicFailure if the property wasn’t present in the markup.

Reading in Xaml throws Catasthrophic failure

Beware the decimal separator

Dashed line in Xaml

0 Comments »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a comment

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
(c) 2010 Szili | powered by WordPress with Barecity