Posts Tagged Silverlight

Cannot load HTML template: No launch page defined in template at c:\Program Files (x86)\Microsoft Expression\Encoder 4\Templates\en\…

While trying my hands on Expression Encoder 4, I came across this issue that my template was not loading . When I checked my Activity log I found that:

Cannot load HTML template: No launch page defined in template at c:\Program  Files (x86)\Microsoft Expression\Encoder  4\Templates\en\SmoothStreamingMediaElement.
Cannot load HTML template: No  launch page defined in template at c:\Program Files (x86)\Microsoft  Expression\Encoder 4\Templates\en\PlugInMSSCtrl.
Cannot load HTML template:  No launch page defined in template at c:\Program Files (x86)\Microsoft  Expression\Encoder 4\Templates\en\OfflineShared.
Cannot load HTML template:  No launch page defined in template at c:\Program Files (x86)\Microsoft  Expression\Encoder 4\Templates\en\MediaPlayer.
Cannot load HTML template: No  launch page defined in template at c:\Program Files (x86)\Microsoft  Expression\Encoder 4\Templates\en\ExpressionPlayer.
 

The reason for this Error was due to the version change. In Expression Encoder 4 > Templates tab is separated from output tab. So simply I added the tab & selected appropriate template I wanted & the error was removed. It also created the necessary packages required

To Add the Templates Tab, simply go to Windows option and Click Templates.

Tags: , ,

AG_E_PARSER_BAD_PROPERTY_VALUE

Error Reporting in Silverlight is really bad. One of the most common error you see whiled developing a Silverlight application
is AG_E_PARSER_BAD_PROPERTY_VALUE.
This error mostly occurs due to following,

Version Change in assemly while you are working in the same code (i.e. you used version x initially and later on you changed it to version x + y ). Some Assemblies in 3rd party control when upgraded do not support few older properties or methods.

Your XAML code is referring to some event which is not present in the code behind file. Make sure that all XAML code has relevant code in code behind file. (Remove any unnecessary Events from XAML and CS files)

Your XAML code has repeated the same code again, causing a clash.

Hope this helps

Tags:

Paying the bills.!