When creating a GUI-plugin you are basically either creating a usercontrol (ascx) or a webform (aspx). The problem with this is that when you deploy your plugin you have to deploy both an assembly and a second file. The location of the second file is of utmost importance since it is defined in the GuiPlugInAttribute's Url property. Is this a problem? Not in most cases, but once in a while it is. Can it be solved? Of course...
More...
I just came back to Stockholm after spending a few days at Oredev in Malmö. Oredev turned out to be a fantastic event. I arrived in Malmö late Tuesday afternoon and checked in to my hotelroom in the center of the city. Later that evening I got in my "costume" aka suit. I very rarely wear a suit and instead stick to baggy jeans and a hoodie... But since the speakers dinner that night was in the Town Hall, I went for a suit. It ended up being a bit overdressed, but hey...I like looking good once in a while...
More...
The problem I wrote about earlier talking about the JavaScript bridge failing when the plug-in is in a div that has it's display set to hidden, is still in Silverlight 2 RTW. But I figured out why. When the plug-in is in a hidden div, the bridge doesn't work, and showing the div from JavaScript and calling the plug-in directly after isn't working either. I tried doing the following, without success:
[code:js]
var hostDiv = document.getElementById("silverlightControlHost");
var plugin = hostDiv.childNodes(0);
hostDiv.className = "hostDivVisible";
plugin.content.ScriptableObjectRef.CallMethod();
[/code]
More...