KyleKatarn

I've found an acceptable workaround by extracting the version from the product name (and not product version) from the registry (install section) AND adding the 3'rd digit from main exe file version properties. Therefore, in next release of SUMo, Paint.NET will appear as 3.5.10.4297. Is this satisfactory for everyone ?

I'll find a specific workaround then... http://www.kcsoftwares.com/bugs/view.php?id=1387 Btw how would your update deal with v3.11.0 (=3.110) if you previously released a 3.1.11 (=3.111 > 110 !!) I'd have suggested to use revision number (4th digit) to do the trick...

I'm the developper of SUMo and i don't see any other solution than applying a specific processing for your product, splitting the 2nd digit in two : 1st digit appart and the rest. But this won't work if you intend to use same versionning for 3.10.2 (3.102 -> 3.1.02 -> wrong detectino !) Using an external update manager make sense since it allows to detect that an update is available BEFORE you need to use your software. Changing the way you tag version would help both MSI and SUMo issues. Thanks !

Root cause found ! It comes from the versionning system used by Paint.NET : v3.5.9 is identified as v3.59. Therefore v3.5.10 is identified as v3.510 and rejected by SUMo due the following limitation in SUMo : http://www.kcsoftwares.com/bugs/view.php?id=542 Any chance to get PdN using a more straight forward version identification in coming versions ? No workaround at SUMo level because 3.510 could be 3.5.10 or 3.51.0...

Sorry, no known limitation in SUMo so far. Paint.Net page in SUMo shows that nothing is reported above v3.59 : http://www.kcsoftwares.com/sumo/view.php?ProductName=Paint.NET&Company=dotPDN+LLC I'll investigate... would you accept to do the same on your side ? Kyle