Report a Silverlight Bug

Re: Re: Re: Re: Re: Silverlight 2 Beta Bug?

Bijoy Thangaraj — Thu, 06 Nov 2008 11:36:20 GMT

What were those differences?

Re: Re: Re: Re: Silverlight 2 Beta Bug?

peterdungan — Thu, 30 Oct 2008 15:38:04 GMT

Sorry I found that the error I was getting was because of some differences in xaml syntax when I upgraded - it wasn't due to this bug

Re: Re: Re: Silverlight 2 Beta Bug?

makkros — Wed, 29 Oct 2008 09:07:13 GMT

Strange, because with the final release it worked for me .

I have the base UserControl declared in XAML and the sub UserControl in the code only.

Re: Re: Re: Silverlight 2 Beta Bug?

peterdungan — Tue, 28 Oct 2008 20:36:31 GMT

I'm getting this error after trying to update a beta 2 project to rtw.

It worked fine in beta 2.

Should it also wrk ok in rtw, or does it indicate the update didn't work properly?

Re: Re: Silverlight 2 Beta Bug?

makkros — Wed, 24 Sep 2008 09:22:11 GMT

Hi all,

does anybody has found a workaround to this problem?

Yi-Lun Luo - MSFT:

It's true that if the base UserControl is declared in XAML, the sub UserControl can only use code. But due to some internal parser issues, currently even if the sub UserControl only uses code, you'll get errors.

I have urgently to solve it, otherwise I have to change all my application logic.

thanks

Re: Re: Silverlight 2 Beta Bug?

makkros — Wed, 17 Sep 2008 11:28:51 GMT

what about the solution of this problem? Does this problem is solved in the future release? Actually I can't run my silverlight application and I need to kwow it in order to plan the update that application.

Thanks in advance

Re: Re: Silverlight 2 Beta Bug?

mchlSync — Tue, 29 Apr 2008 07:34:13 GMT

Yi-Lun Luo - MSFT:
Hello, this is a known issue. It's true that if the base UserControl is declared in XAML, the sub UserControl can only use code. But due to some internal parser issues, currently even if the sub UserControl only uses code, you'll get errors. Our developers are tracking this issue. But sorry I can't give you more details at this time...

Thanks for your reply. Yi-Lun.

Re: Re: Silverlight 2 Beta Bug?

Yi-Lun Luo - MSFT — Tue, 29 Apr 2008 06:33:37 GMT

Hello, this is a known issue. It's true that if the base UserControl is declared in XAML, the sub UserControl can only use code. But due to some internal parser issues, currently even if the sub UserControl only uses code, you'll get errors. Our developers are tracking this issue. But sorry I can't give you more details at this time...

Re: Silverlight 2 Beta Bug?

mchlSync — Tue, 29 Apr 2008 05:47:15 GMT

Hello,

The problem is that we can't have XAML in Base Control. Is it possible for you not to use XAML in BaseControl?

Re: Silverlight 2 Beta Bug?

Necroman — Sun, 27 Apr 2008 09:42:43 GMT

I use different way, when inheriting objects:

BaseControl = It is inherited from User Control. It has XAML.
MyControl = It is inherited from BaseControl. It is a class that doesnt have XAML. Additional controls and methods are added in C# code in constructor.

In classic WPF it works without a problem, but in Silverlight 2 I still get the error, when I try to instantiate MyControl.

MyControl control = new MyControl();

LayoutRoot.Children.Add(control);

It crashes with AG_E_PARSER_BAD_TYPE when calling InitializeComponents() in BaseControl.
Just try it and you'll surely get the same error message.

Btw. In your example, http://michaelsync.net/demo/SilverlightApplication10.zip you are adding the Base class <ctl:SimplyActivity /> into Page, try adding the inherited class <ctl:SilverlightControl1 /> and you get the exact same error.

Re: Silverlight 2 Beta Bug?

arshadm — Sun, 27 Apr 2008 06:39:13 GMT

Actually, it doesn't work from the XAML either because afterwards I noticed that Page.xaml was uing ctl:SimplyActivity rather than the subclass ctl:SilverlightControl1, when I changed that it gave the same error.

I think I can understand why this might not be allowed in the current circumstances because it doesn't really make sense to have two separate XAML in the class hierarchy (which one is the real user interface because there can only be one root control in each user control).

My original requirement though was much simpler and shouldn't cause a problem as far as I can see, I wanted a base class with XAML. This base class may be abstract, a derived class would then provide the actual implementation for the event handlers and other logic. I think this would be a very useful feature, but obviously since I am a Silverlight newbie it might open up a can of worms which I don't understand.

Regards.

Re: Silverlight 2 Beta Bug?

mchlSync — Sun, 27 Apr 2008 05:43:02 GMT

You are right. Adding the control from code is giving you this problem... Is it possible for you to add the control in XAML? (Like I did in my sample)

Re: Silverlight 2 Beta Bug?

arshadm — Sat, 26 Apr 2008 17:00:32 GMT

Sorry, syntax error in code

Canvas.SetTop(control, 50);

Canvas.SetLeft(control, 50);

But still gives same exception.

Re: Silverlight 2 Beta Bug?

arshadm — Sat, 26 Apr 2008 16:42:13 GMT

Hmm, your code works if the subclass is treated as a control via the assembly.

But, if I add the following line to Page.xaml.cs then it throws the error I mention, and I am not sure why anymore because it works when it's used via the Xaml but not in code.

public Page() {

InitializeComponent();

UserControl control = new SilverlightControl1();

LayoutRoot.Children.Add(control);

Canvas.SetTop(50);

Canvas.SetLeft(50);

I changed the Page.xaml to remove the mention of the control to :-

</Grid>

This should be doing in C# code what the xaml is doing, but it throws the exception I mentioned above.

Regards.

Re: Silverlight 2 Beta Bug?

mchlSync — Sat, 26 Apr 2008 15:02:40 GMT

Hi,

I have tested your code. It's working fine. (I think there are some typo errors in yourposts)

You can download the code from this link. http://michaelsync.net/demo/SilverlightApplication10.zip