The other two problems will disappear the moment your app/account is evaluated and accepted by the Microsoft team for upload in the store. Here is a similar situation on the the MSDN forums.
So if I understand correctly I can just edit software version as seen in attachment "software_version.png" to 4.5.3 and problem should be gone? Yes, that is correct. Regarding the order problem. We will address this issue ASAP, thanks for the feedback. Problem #2: I attached screenshot wi...
Sure, we're curious too. Can you share with us the MSI you tried to convert with our converter? So we can see why it did not detected your shortcut correctly.
Hi, Problem #1 : The version you set in Package Information page, in your project, sets the forth field (i.e. revision) to value 787. It appears the Win Store does not allow setting this fourth version field. The solution is to edit your project and set your version to this value: 4.5.3 Problem #2 :...
Hi and welcome to our forums, From you question it is not clear to me if you are using Advanced Installer to build the AppX or our Desktop Bridge Setup Converter. Since you mentioned Product Details page I assume you are using Advanced Installer. Now, in your Advanced Installer project, in the left ...
Hi and welcome to Advanced Installer forums, Starting with Visual Studio 2017 Microsoft has indeed introduced some changes in its setup package, but these are not related to any "end of the MSI". To see a detailed explanation of the changes MSFT did on their VS installer packages, I recomm...
Hi, Hrm, that's unfortunate. Do you guys plan to work on this ? Unfortunately this is not on our roadmap for the near future, due to an architectural limitation from Advanced Installer. In theory, I could accomplish the same thing by cloning the AIP file and then Closing an AIP file will lead to big...
Hi, Each MSI will know to handle the removal of the old version, if the upgradecode is the same, as you said. The only condition you need to make sure is followed, is for the latest MSI packages you deploy to have a higher version number than any of the old ones. The higher version number will trigg...
Hi, 1) We analyzed this situation in the past and decided not to force the user to have the EXE output because of the scenario mentioned in your second question. We have users that build also an MSI from the same project, mostly used by IT admins to deploy it silently over the network with SCCM, Act...
Hi and welcome to our forums, To achieve what you want you need to create two separate MSI and bundle them. Here is what you can try: - create a separate MSI that installs only the certificates as you do now - then take this MSI and add it as a pre-install or feature-base prerequisites, in Prerequis...
Hi, As you said, the option Mihai recommend applies only for normal files, from File table, not for assemblies. I don't believe this is possible for assemblies with the same version number. Here is a similar talk on SO.com . The version number you define in Assemblies page, or directly in your assem...
Hi, This is a problem we had in older versions. We did not got any new reports of this occurring within the last released versions. Can you please tell us what version are you using? If you are using an older version and it is possible to try a newer one, please install it side by side and give it a...
Hi, In the current software I don't see these options. I don't want to be mean :) but I guess you are using the PRO edition and the features I mentioned are available in the Enterprise project, thus you need an Enterprise license. The same is valid for the properties appearing for a few seconds on t...
Hi and welcome to our forums, can I apply 13.7 patches onto existing 13.3 patches/installations? Yes, you can. However, we recommend creating images for patches and the patch itself with the same version. You can keep version 13.3 side by side with 13.7, this is supported by us, and if you need to c...