![]() ![]() I've never done this myself, so your testing will be critical. This may be a problem because by clearing the contents of the string value in (2) above, you are manipulating the core Windows Installer values for the msi install itself. You will need to be sure that Silverlight can upgrade properly. You will need to check very carefully that the msi uninstall that your wrapper runs does then uninstall it properly.Ģ. Then you should still see one Microsoft Silverlight entry in Add/Remove and it should call your custom program. Do NOT delete the value itself, just change the string contents from "Microsoft Silverlight" to "" (blank, no quotes) ![]() HKEY_LOCAL_MACHINE\SOFTWAR E\Classes\ Installer\ Products\D 7314F9862C 648A4DB8BE 2A5B47BE10 0\ProductN ame I think my question can be resumed as follows: How can I change ARP behavior from "msiexec /x\Uninst allStringĢ. I want to avoid extracting Microsoft's setup.exe to manually modify the MSI/MSP since I would loose the automated removal of older silverlight versions. I found another key ( HKLM\SOFTWARE\Classes\Inst aller\Prod ucts\D7314 F9862C648A 4DB8BE2A5B 47BE100) which seems to modify whatever is displayed on ARP in terms of application information (like name and version information) but it doesn't have any value that seems to provide information on how ARP knows how to remove the application. I tried to modify the HKLM\SOFTWARE\Microsoft\Wi ndows\Curr entVersion \Uninstall \\UninstallString key to call either the wrapper or a script that removes the branding, but it doesn't matter what I change on that key it doesn't affect the behavior of ARP. The problem is that after succesfully installing everything (my wrapper adds the registry keys, then calls the setup.exe with the switches, which in turns calls microsoft's MSI MSP), when uninstalling, obviously the branding remains, since the entry on ARP calls only the MSI MSP, and has no reference to my wrapper. Then I need to wrap this setup with another executable (InstallAware v12.0 wrapper) in order to apply my client's branding (some registry keys) at the moment of installation and make the package in a way that removes those keys at uninstall through Add or Remove programs (ARP). Silverlight is expected to reach end of support in 2021 with support for several browsers and OS platforms already ended in 2016. the executable of the Silverlight application to be migrated. I am building an installation package for the latest iteration of Microsoft Silverlight, by using the setup.exe installation switches conveniently pre-programed by windows: /q /noupdate and /doNotRequireDRMPrompt. On the OpenSilver web site there is also the possibility of submitting a XAP file, i.e. NET, C, and XAML, as with Silverlight, with the notable difference that applications created with OpenSilver run on all current browsers, including Chrome, Edge, Firefox and Safari, without the need to install a plugin. I have been searching an answer for this without success, so it's time to use the ultimate source: EE! It is a development tool allowing developers to write web applications using. ![]()
0 Comments
Leave a Reply. |