GDR's. I just wrote an application for a large organization. I upgraded the application to SL 4. Everything was working OK (except for the browser problem). I made a couple of tweaks over the weekend. This morning, the users started contacting the administrator because the application was requiring that they update their version of Silverlight. They JUST updated to the current version of 4 last week and now another upgrade. The admin just wrote me a very. They all have 4. 0. Of course, it takes a chunk out of mine to fix it. What would be even worse is if I had a broadly- distributed application that produced revenues and those revenues suddenly.
IMO, this automatic GDR update policy is VERY detrimental. I need a little time to warn people and I can't just have the app stop working because someone decided to come out with a new release. I've read Tim Heuer's discussion on this. Unless I'm misinterpreting it, he's telling us we have to defeat the automatic update policy. Keep in mind that I have. SL version on this application since I had the client upgrade to 4. VS2. 01. 0 has somehow decided to just go ahead and do this for me somehow. 4 GDR: 4.0.50401.0: 15 de abril de 2010 . El 18 de noviembre de 2009 en la Conferencia de Desarrolladores Profesionales celebrada en Los Microsoft Silverlight; Developer(s) Microsoft Corporation: Initial release. Silverlight for Windows Phone 7.5 is based on Silverlight 4. A Silverlight application being edited in Microsoft Visual Studio. Microsoft Silverlight; Sviluppatore: Microsoft Corporation: Ultima versione: 5.1.50709.0 (13 settembre 2016) Sistema operativo: Microsoft Windows. 4 GDR 4: 4.0.60310.0: 19 aprile 2011: 4 GDR 5: 4.0.60531.0: 14 giugno 2011.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |