We’ve just released an update to our Silverlight Enterprise Deployment guidance/whitepaper.  While a lot of the information from the first version of the guidance (targeted at Silverlight 1.0), we made some minor adjustments outlining the specifics for the updated Silverlight installer and documented some of the command-switches and their behaviors.  The guidance covers: Using Windows Software Update Services (WSUS) Group policy Microsoft System Center Configuration Manager (SCCM) Manual install options Maintaining and detecting version It’s a great guidance document to...

one of the things interactive developers sometimes (especially with new technologies like silverlight, flex, etc.) have to worry about is 'what if the end user doesn't have XYZ installed?' -- something that is likely going to be a question when implementing something so new like silverlight. in silverlight, if the user doesn't have the plugin installed, they are presented with a 'get silverlight' badge.  it really doesn't explain much about *what* silverlight is, or what they'd be missing (i.e., interactive, rich content) if they don't install it.  to me, the default badge doesn't pass the mother-in-law factor test.  i first wrote...