So I know now that the debug assemblies have been intentionally left out of the Silverlight runtime to save space. For that reason I get good detailed error messages on my local machine that has the Silverlight SDK on it, but I don’t on a computer with the runtime only. I get the ubiquitous, “Debugging resource strings are unavailable.”
Unfortunately my requirements are a bit unique. I need to include the debug assembly (not sure which one yet) that will give me details of a regular expression error. And so essentially I want to include the dll in the xap if I can.
The problem is that I can’t seem to do this. I’ve tried adding the debug dll’s as references and setting them to “copy local.” And I’ve tried adding them into the project as content. But in fact, with either method the xap hardly grows in size and the error message doesn’t change.
Any ideas?
You’ll still need the actual Silverlight Developer Runtime to be installed (thus you get the errors etc on the machine you had the SDK installed on). Adding the debug assembly into a production solution and accessing it via the non-developer runtime isn’t possible.
Scott Barnes / Rich Platforms Product Manager / Microsoft.