Well desinged , My wish list would be to add the exception handling block via html bridge as part of the template. it is a very good way to surface the errors no matter which browser or policy is applied to the browser.
It can also be an init parameter like Debug=On etc.
Very good tool though , I have built 2 projects already.
I had a couple of teething issues initially, but I managed to solve them. This tool adds some great support for being able to customize aspects of the silverlight/sharepoint link. The level of support I recieved as well from the tool's dev team with my issues was great.
I am deploying to a farm as well, I got past the sandboxed issue, but now I get this:
Error occurred in deployment step 'Activate Features': Failed to instantiate file "SitePages/SilverlightApplication1WebPartPage.aspx" from module "SitePages": The specified list does not exist.
Same problem here. I have a farm solution where I want to include the Silverlight app in (all under the same SharePoint solution), but as soon as I added the SL app, the Silverlight SharePoint Web Parts interferes with all deployment saying
"Error 1 The project Item "SPBackupSLWebPart" must be deployed as part of a sandboxed feature. Move the project item to a feature where the Sandboxed Solution property of the project is set to true. C:\Users\Administrator\Documents\Visual Studio 2010\Projects\SPBackup\SPBackup\SPBackup\Features\Feature1\Feature1.feature SPBackup"
What gives? Can this really work in a farm solution??
Yes, it can work in a farm solution but there's a little configuration change that was not documented.
Took me a while to find it too.
1. Find the file SharePointProjectItem.spdata in the project folder
2. Change the SupportTrustLevels attribute from SandBoxed to FullTrust or All
For more info on what this config means, check out the link below:
Hope this helps everyone here. Btw, this is a really great tool (of course minus the little hiccups) but it still saved me a lot of unnecessary work.