Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

Dark Jester — Wed, 07 Oct 2009 21:11:19 GMT

Ran into this today. One thing of note is that when I opened the .Xaml page in Expression Blend, it gave me the exact location of the error. Better debug features in Blend than in SL itself? :)

Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

NewsPeeps — Sat, 08 Aug 2009 22:36:10 GMT

Thank you for submitting this cool story - Trackback from NewsPeeps

Silverlight Tips of the Day - Summary Outline

Silverlight Tips of the Day - Blog by Mike Snow — Mon, 06 Apr 2009 22:20:00 GMT

The purpose of this post is to create an outline summary all the blogs from my Silverlight Tips of the

Silverlight Tips of the Day – Week 12

Visual Web Developer Team Blog — Mon, 06 Apr 2009 22:13:16 GMT

Most Recent Posts: Silverlight Tip of the Day #106 - Setting Default Browser from within VS Silverlight

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

sandeepsaxena — Thu, 12 Mar 2009 07:46:36 GMT

How should I fix this in my xaml.vb file ?

Programming with Silverlight, WPF & .NET » AG_E_PARSER_BAD_PROPERTY_VALUE

Programming with Silverlight, WPF & .NET » AG_E_PARSER_BAD_PROPERTY_VALUE — Sat, 28 Feb 2009 10:48:49 GMT

Pingback from Programming with Silverlight, WPF & .NET » AG_E_PARSER_BAD_PROPERTY_VALUE

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

tgrand — Wed, 25 Feb 2009 16:30:09 GMT

Thanks Mike, that's great news!

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

mike.snow — Mon, 23 Feb 2009 16:45:22 GMT

Thanks for your feedback. I have talked with people on the Silverlight team and they are working to make great improvements in this area.

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

tgrand — Mon, 23 Feb 2009 15:27:16 GMT

Agree with the previous posters. These errors often shed little or no light on the problem. Not much fun to debug, especially in those nasty cases when the problem only happens on 2 machines out of 10.

Better error reporting would be a huge improvement to Silverlight.

The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE — Mon, 23 Feb 2009 14:14:03 GMT

Pingback from The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

Silverlight Cream for February 21, 2009 -- #524

Community Blogs — Sun, 22 Feb 2009 01:46:01 GMT

In this issue: ScrumWall, Mike Snow, Joel Neubeck, WorkSight Blog, Robby Ingebretsen, and Bill Reiss

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

wireplay — Sat, 21 Feb 2009 04:40:01 GMT

Can we just say, politely, that error reporting in Silverlight is lacking? Silverlight team should put a LOT of effort into this area because it is really bad right now. I don't understand the complexities, I am sure, but it is a place to make some improvements, IMO.

re: Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

obsid — Sat, 21 Feb 2009 04:31:38 GMT

Dont think for a second this is the only place that error occurs. I have had this error hundreds if not thousands of times, for a variety of reasons. Your lucky that you got a stack trace at all. Alot of the time it just comes back that a call to XcpImports failed with an error code of 0x00000 or something similar. I see alot of problems with attached depeancy properties if everything isnt exactly right. There are tons of places that cause this error, and it isnt clear at ALL which one of the dozen possible causes is the reason. All the error messages that start with AG_E_... are really crappy in telling you how or why something failed.

Silverlight Tip of the Day #96 – The meaning of AG_E_PARSER_BAD_PROPERTY_VALUE

Microsoft Weblogs — Sat, 21 Feb 2009 03:15:46 GMT

If you ever run into this error when running your application you might be a bit perplexed by its encrypted