ldlx

Since 4.3 the customization of the property "PROGRAMSGROUP" is broken. The shortcut is in the start menu's root instead of the desired folder that is specified inside the MSI installer or transform file. Can you fix that please? Thanks!

I experienced the previous issue of the 3.5.11 beta installer again. While 3.5.11 beta was installed on my computer I extracted the MSIs using the /createMSI parameter. The freshly extracted MSIs for 3.5.11 final contained the modifications I made for the currently installed 3.5.11 beta installer (using a tranform file during install of 3.5.11 beta), so the properties PROGRAMSGROUP and DESKTOPSHORTCUT were "customized" in the 3.5.11 final MSIs.

I just wanted to add the new (and clean) MSI to the group policy for deploying Paint.NET. The version is shown as 3.61 instead of 3.5.11. Is this "just a typo" or is this version number intended to be displayed? Also both the x86 and x64 versions are updating the x86 and the x64 version by default. Is this behavior intended? Maybe both packages have the same upgrade code.

Hi, with previous versions of Paint.NET I got used to deploy it as MSI via group policy in my environment, customizing the DESKTOPSHORTCUT and PROGRAMSGROUP entry in the MSI file. The 3.5.11 MSI won't let me use my previous transform file :-/ So i checked out the first MSI, extracted while 3.5.10 was still installed. From the previous installation, the /createmsi switch created the msi containing my customized parameters - hard coded! Afterwards I uninstalled Paint.NET and extracted the MSI again with the /createmsi switch. Now the extracted MSIs didn't contain customized parameters and what was confusing me at the first sight, the PROGRAMSGROUP entry was not there anymore! Creating the transform file by adding the missing value manually it was easy to recreate the transform file for the new version's MSI. It would be nice if the PROGRAMSGROUP entry would have been there. But I think extracting the MSIs from the original setup file shouldn't overtake customized values hard-coded, although an old version is installed on the specific machine with customizations made by a transform file from a previous installation. The new package should extract cleanly, and only when installing the MSI on a machine respect the existing customized values at the machine where it is installed on. But beside this observation I like the way you provide a MSI from another installer in almost no time and without the need to have any frameworks like WiX installed. Another question: will the future version 4.0 will contain instructions to uninstall previous 3.5.10 and older versions if it is detected on the target machine? ("major upgrade")