Advanced Forum Search Results
-
The docs are actually public. E.g.: http://msdn.microsoft.com/en-us/library/system.windows.messaging.localmessagereceiver(VS.96).aspx
-
This is indeed weird and seems like a glitch. I will follow up with the doc owners.
-
Yes, as previous poster noted, access to the HTML DOM by the VE control is very likely the problem when the app runs out of browser.
-
tgrand: the first prompt you're seeing seems to be the time-bomb dialog. Silverlight 2 Beta 1 was time-bombed to expire after a certain date.
The second dialog indicates an error which is raised by the Silverlight app activation mechanism when it is unable to load an assembly into the appdomain. What is a mystery to me is why either ...
-
Guys, let's break down this task:
You're downloading a XAP on-demand
You're extracting the app manifest
You're parsing it (via XamlReader which constructs a strongly typed element tree)
You're traversing the manifest to look for AssemblyParts
You're pulling the Source value
You're extracting ...
-
This is a recent breaking change that restored the singleton nature of Deployment object, as original conceived. You can workaround by using XmlReader instead of XamlReader to parse the manifest file. You lose strong typing, but in most (if not all) cases this is not central to your goal of looking at attribute values in the manifest (e.g. ...
-
Ah, sorry I meant ActualHeight/ActualWidth. Those are the values calculated as part of a layout pass -- these are reliable natural dimensions because there is no stretch on the image.
Width/Height default to "auto" which is Double.NaN. You're on the right track now.
-
Yes I know. However in HTML, programmatic creation of an OBJECT tag usually boils down to doing adding a new element to the DOM, say using document.write("<OBJECT ..."); If there were a different way, believe me, we'd use it in the script within Silverlight.js :)
-
I believe these forums use Silverlight 1.0. If you can see interactive content here, can you right-click, choose Silverlight Configuration and look for the version number? Those other sites you visit must be using a beta of Silverlight 2 which is why you're seeing the "install Silverlight" badge.
Last night we released Silverlight 2 ...
-
BitmapImage.DownloadProgress event still remains. That is in fact what's important -- it is what you set as Image.Source.
See http://msdn.microsoft.com/en-us/library/system.windows.media.imaging.bitmapimage.downloadprogress(VS.95).aspx