Silverlight Display Web Part and Why You Should Always Do Least Priveleged Testing

Home » SharePoint Development » Silverlight Display Web Part and Why You Should Always Do Least Priveleged Testing

Silverlight Display Web Part and Why You Should Always Do Least Priveleged Testing

Posted on

A few weeks ago I whipped up a quick display web part for Silverlight projects and posted it for download.  I was in a hurry just to get something done and thought I’d share it for everyone who might need it but, alas, I failed to completely test it.  When I enabled anonymous access for the site it was deployed on all hell broke loose and I had to go rewrite it and rebuild the solution package (a few other folks had the same problem).  That’s what I get for breaking my own rules and not doing least priveleged testing before I released it.  So an official slap on the hand to myself for bad coding practices.
 
The new version can be downloaded here.  Just retract and remove the solution in Central Administration then re-run the deployment batch file in the zip archive.  You shouldn’t need to deactivate the feature first but you might want to just to be on the safe side. 
 
My apologies to everyone who downloaded the previous version and had issues with it.  Feel free to curse me soundly when you see me at the SharePoint Conference