*** Clarification Point ***
Whenever a custom silverlight control is to be added to an ASPX page, that control needs to be implemented as a page.xaml file and included in the XAP file, then each XAP file that houses each control needs to be added explicitly in the silverlight tag.
i.e.
MyCustomControl is implemented in Page1.XAML which generates MyCustomControl.XAP file
MyOtherControl is implemented in Page1.XAML which generates MyOtherControl.XAP file.
To impelement in the ASPX mark up you would have
<asp:ScriptManager ID="MyManager" runat="server"/>
<asp:Silverlight id = "MyControl" runat="server" Source = "~/ClientBin/MyCustomControl.XAP" />
<asp:Silverlight id = "MyOtherControl" runat="server" Source = "~/ClientBin/MyOtherControl.XAP"/>
There is no way to implement a library of associated controls in a .xap file and choose which control to include in an ASPX page correct, one XAP file per Control?
Secondly, if there are custom events on the control there is no way to capture them on the ASPX.cs file correct? Is the only way these can be captured via JS?
I know if I had a pure Silveright application this would be feasible, but complete migration vs. cherry picking ideal implementation points and gradually migrating over feels like a much more feasable transition for both users and stake holders.
Thanks.