Register   |   Login

 

Spark Your Solution

 Scott's Technology Blog Minimize

By Scott Davis on 6/12/2008 12:18 PM

After upgrading from SilverLight 2.0 Beta 1 to SilverLight 2.0 Beta 2 I started receiving the following strange behavior.  The project would compile just fine (and execute with no issue), but he design view of my XAML page stopping showing the preview.  Although the project compiled just fine, with zero failures, if you look in the error list, you would see an error.

AG_E_UNKNOWN_ERROR   in file Page.xaml

Read More »

By Scott Davis on 6/11/2008 8:55 PM

 
As part of a project I am working on, I wanted to be able to reuse a storyboard object to animate several controls the same way. At the end of the animation (the animation complete event) I needed to perform a final modification to the object. The problem with the animation object is that you can’t get back a reference to the object you animated. You can define which object to animate in two ways.  In the XAML tags, you set the name of the object (Storyboard.TargetName) on the animation object attributes. In the code behind, you use the Storyboard.SetTargetName([animation object],[string]) or Storyboard.SetTarget(([animation object],[target object]). When using the SetTarget you pass the object itself.
By Scott Davis on 6/11/2008 5:16 PM

Don't just install SilverLight 2.0 Beta 2 overtop Beta 1, despite what you might hear from people for whom it worked.  You may encounter this problem, posted by Tim Anderson.

http://www.itwriting.com/blog/?p=665

Hopefully you won't have a problem, or if you do the process of uninstalling and installing again is easy enough of a solution.  However, if you are like me it won't work and you should follow these steps, posted by BradleyB.

Read More »

By Scott Davis on 6/10/2008 10:30 PM

In both SilverLight 2.0 Beta 1 and Beta 2, I've experienced the situation where my break points are not being hit, while debugging my application in Visual Studio 2008.  It took a few attempts at figuring out why this was happening, but the answer was to clear the browser cache.  I have not determined exactly what causes the browser to cache the SilverLight application.  It appears to happen only intermittently for me, with a need to clear the cache a half dozen times a day. 

Notice that your break points will have a question mark on them, when the browser is running the cached version.  Additionally, of course, any recent changes you made to the application won't be reflected, when running the cached version, despite a browser refresh (F5).  You must go into the browser (IE6) options and clear the cache, then refresh.

 Print   
 Blog Dates Minimize

 Print   
 Search Minimize

 Print